search for: headefile

...d to do is add "../whatever/src" to your include path (e.g. > -I with gcc) > I don't see a reason to add anything to the include path, it just doesn't make sense and nothing on the face on the planet can convince me otherwise. Look, I need to #include "../whatever/src/headefile.h", why is that I need to do something else, if #include "../whatever/src/headefile.h" does what exactly what I need? If #include "../whatever/src/headefile.h" produces an error, then "../whatever/src/headefile.h" has a problem. Speex doesn't have multiple lev...

I'm just curious, who and why came up with that strange way to write includes: #ifdef _BUILD_SPEEX # include "speex_types.h" #else # include <speex/speex_types.h> #endif I personally consider it a bug. If I use speex then obviously I should not have _BUILD_SPEEX defined. The broken behavior happens in this simple scenario: 1) I check out latest git version to ./src/speex 2)