On 4/28/04 at 7:17 AM Jon Berndt wrote:
>
>Many of the rest of them seemed to simply hang, but no sound was ever
>produced. I wonder, though, if your stuff was being used here, because I
>already have libopenal32.a in /usr/local/lib. I recompiled all the tests.
>

The tests compile and link with ../src/libopenal.a, so unless you've hacked
their build script or replaced that lib with Norman's then you'll still be
linking (the tests) against the original.

>Are we CygWin users going to be stuck with the previous codebase because
>openal doesn't work under CygWin? Or, do we have a choice with audio APIs?
>I'm hesitant to do a CVS update on the FlightGear tree at the moment
>because
>I'm not sure what the state of this OpenAL stuff is ... has it been
>formally
>introduced into FlightGear CVS, and does it replace the current audio
>system?
>

At the moment the current CVS won't compile on Cygwin - there is no option
to use the old audio code (that I know of).  This isn't a complaint though
- I think the long term benefits should far outweigh the short term pain.

Cheers - Dave



This message has been scanned but we cannot guarantee that it and any
attachments are free from viruses or other damaging content: you are
advised to perform your own checks.  Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.


_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to