[stinos]

Really diggin the idea of using include files to figure out dependencies. Also seems ideal for beginners: look up the number of questions on SO asking 'which library to include for xxx.h' by people who don't yet grasp the difference between compiling and linking. Here you just say 'hey, I have this header, that's for this lib', directly. But it won't be for me though (well, this version at least, who knows what the future brings): it puts constraints on the directory structure used and on how you include your files. And is probably gcc only. Yielding basically none of my projects a candidate for testing this. But still, nice.

[vezzy-fnord]

Also seems ideal for beginners: look up the number of questions on SO asking 'which library to include for xxx.h'

Pretty sure pkg-config can help with that. Don't see why you need SO.

[nightcracker]

Because beginners have no clue what pkg-config is?

[stormbrew]

Also it's the first-step problem of knowing what to ask pkg-config (or any other tool that can tell you). Header file names don't always map to the library or package name.