On 5 May 2010, at 10:41, HB-GRAL wrote:

> I will call it *LUT just not to add another thread to a long long list. 
> Took me some days to read about this problem on OSX. I apologize that I 
> can not solve my new compiler issues with this 
> holy-book-of-keeping-alut-thread ;-)
> 
> Recent SimGear CVS change in Soundmanager push me to install a new 
> ALUT.framework (my recent OpenAL installation with "fake" alut.h on OSX 
> worked well until last monday).
> 
> I tried to work with new changes but I get undefined symbols 
> "alutGetError" and "alutGetErrorString" from SoundManager when I try to 
> compile FG CVS (SimGear CVS compiles well also with new SoundManager).
> 
> First question is probably: Can you give me some hints how I have to set 
> correct PREFIX path with --with-openal-framework= when my new 
> OpenAL.framework exists at /Library/Frameworks/?

Right, it sounds like you are pretty close. The new situation is as follows:

- don't touch your standard Apple OpenAL *at all* (apart from maybe the ALCvoid 
-> void tweak which I suspect we are stuck with)

- grab ALUT.framework from here:
        http://files.goneabitbursar.com/fg/alut-osx-universal.zip
        (temporary location)

- put the framework somewhere sensible, probably /Library/Frameworks is easiest

- If you are using autoconf/automake, you will need to add -framework ALUT to 
someplace; I haven't made the autoconf changes yet since I wanted to get some 
feedback on the code parts of the change before we completely commit to this 
new approach (if you use Tat's XCode projects, you will need to adjust things 
too, but I assume that is obvious)

This should give you a real ALUT 1.1, no problems with the Apple OpenAL, and no 
compile/link problems with SimGear. At least that's the hope! Let me know what 
you experience, because that's exactly what I want to discover in the next 
couple of weeks from other Mac developers. Once I'm sure it works and makes 
sense for people, I will make the configure changes and put my ALUT framework 
somewhere official (and write some Wiki documentation, I guess)

James



------------------------------------------------------------------------------
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to