Hi Vivian, I was very busy these days, so I did not catch up with the mailing list in time ...
I was in the impression that it would be wise to support Freds Build system, though not perfect but one can life with it. >>> 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. Ah now I see, you are using the libs and headers of the unmodified SDK! I was just using my Freds 3rdParty build system in order to catch up and I found no reference that anyone is using the new SDK. Maybe it would be wise to support both for the moment until Fred fixes the 3rdParty Win32 binary distribution defining OPENALSDK when using the official SDK. ... #elif defined(OPENALSDK) # include <al.h> # include <alc.h> # include <AL/alut.h> #else # include <AL/al.h> # include <AL/alc.h> # include <AL/alut.h> #endif > Quite correct, Geoff, but why would anyone be using anything other than the > latest build from Creative Labs? Surely we need to make it all build with > OpenAL 1.1 SDK? > I've given up on this saga. Sound continues to cause a crash > on exit here. We are just chasing our tails. When someone sorts it all out, > I will _try_ to make it compile under MSVC9. > I'll get crashes too in OpenAL exit. (With the Old SDK, aka Freds Build System). But I'll get crashes in the XML Parser in debug mode in the first place, have to sort it out. I thought the OpenAL crashes are just because of a memory corruption way earlier. ------------------------------------------------------------------------------ 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
