Well it can't be too dangerous. It's not like you're going to replace Apple's OpenAL framework with yours, just to test it.
If it was a problem with the way FG uses OpenAL, wouldn't it be a problem on the PPC as well? Unless it has something to do with big versus little endian. On 4/17/06, James Turner <[EMAIL PROTECTED]> wrote: > > On 17 Apr 2006, at 16:32, Arthur Wiebe wrote: > > > Did you try doing your own build of the latest OpenAL source? > > No, that seems like a dangerous thing to do, IMO, since Apple are > supplying OpenAL as part of the OS. I find it hard to believe the > problem is really in OpenAL, since it's so widely used at this point > - my guess was some kind of interaction in the way FG uses OpenAL, > but I didn't get time to look in detail. > > The easiest thing is just to try it, of course - let me know once you > have a candidate build and I'll see what happens. > > James > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Flightgear-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/flightgear-users > -- <Arthur/> - http://artooro.googlepages.com/aboutme
