search for: _build_speex

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) My s...

...headers are included this way by user programs: #include <libavcodec/avcodec.h> But internally, you can't find a single place where ffmpeg includes its own headers using angle brackets. The only headers that are included this way are external and system 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. > > So far so good. > > > The...

Hi On 10-06-21 07:24 PM, Pavel Pavlov wrote: > I'm just curious, who and why came up with that strange way to write includes: I did. Because I think that's the way to go. > #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. So far so good. > The broken behavior happens in this simple scenario: >...

...if test -n "$PKG_CONFIG"; then + PKG_CHECK_MOD_VERSION(OGG, ogg >= 1.1.3, ac_cv_ogg=yes, ac_cv_ogg=no) + src=src + fi +if test x$ac_cv_ogg != xyes; then + XIPH_PATH_OGG([src="src"], [src=""]) + fi AC_SUBST(src) AC_CHECK_LIB(m, sin) @@ -287,7 +297,7 @@ AC_DEFINE([_BUILD_SPEEX], [], [Defined only when Speex itself is build built]) AC_OUTPUT([Makefile libspeex/Makefile src/Makefile doc/Makefile Speex.spec include/Makefile include/speex/Makefile speex.pc speexdsp.pc win32/Makefile win32/libspeex/Makefile win32/speexenc/Makefile - win32/sp...