search for: speexutil

...hat include eachothers' header files (eg. In ffmpeg, avcodec uses avutil etc), and therefore speex doesn't need to include headers from different folders, they are all in the same folder and there is no reason to include them that strange way. If SPEEX had mulple subprojects (like speexdsp, speexutils etc) then to use some speex a programmer would have to add include search path to find speex, but still there is no reason for the speexdsp and speexutil to include each other's headers using <>! I'm not sure how much you care about ms compiler, but it will look in system path for a...

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)