On Sun, 2009-10-18 at 15:07 +0200, Erik Hofman wrote: > Vivian Meazza wrote: > > Patched soundmgr_openal.cxx/hxx and sample_group.hxx with > > > > +#elif defined(_WIN32) > > +# include <al.h> > > > > or > > > > +#elif defined(_WIN32) > > +# include <al.h> > > +# include <alc.h> > > +# include <AL/alut.h> > > Olaf pointed out to me that this wasn't necessary for more than 5 yearss > and indeed AL/* is the recommended place for the header files by > specification. So I'll revert this to section to the way it was before. > > Erik >
Ok, that will break it for Vivian, myself and OTHERS who use the Creative Labs OpenAL 1.1 SDK, which DOES NOT put 'al.h' and 'alc.h' in an 'AL' sub-directory. They are simply in :- C:\Program Files\OpenAL 1.1 SDK\include by default... check it out... So whose 'recommended' ... 'specification' are we talking about? At least change the #elif defined(_WIN32) to say #elif defined(USE_OPENAL_SDK), then we can ALL be happy ;=)) I always thought using the generic _WIN32 would be a no go for those using older/other versions of OpenAL that do use an 'AL' sub-directory... And can this 'include' block not be just in ONE header, like say sample_group.hxx, and then soundmgr_openal.cxx/hxx, etc can include that header... Regards, Geoff. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
