Am 08.11.2011 21:44, schrieb Jörg 'Yadgar' Bleimann:

> What is the #include path? Where do I find it?
>
> Why are these things so brain-shreddingly complicated?

Seems to be typical for libraries. I have yet to see any that comes with 
an easy-to-use build system. Or at least some /standardized/ one, for 
that matter. The tendency there seems to be to try make life for the lib 
developers as easy as possible by using some home-brewn build system 
custom-tailored to their needs, but at the same time making life 
annoyingly difficult for application developers (or end users), forcing 
them to dig through all those different build systems of the libraries 
the app is using.

Okay, maybe I'm exaggerating here. Never mind...

Post a reply to this message