Jari Häkkinen wrote: > Hi again, > > Tanks for the pointers. > > My comments was to elaborate on the consequences of the removed alut > support by Apple. It is dangerous to use any alut.h you find on the web. > As you point out using Creatives alut.h may make things simpler > (macports.org is another option). I used freealuts alut.h which made the > compiler to choose an unexpected path (for macs) in the source during > compilation. The path chosen by the compiler required more alut > functionality than provided by my mac. However, using freealut libs and > alut.h, and Apples OpenAL framework works perfectly, I have done that > for a while. (Now I changed strategy as outlined in other postings in > this thread.) > From what I understand Apple is depreciating those old alut functions (but still keeps hem in the library for backwards compatibility) and is encouraging everyone to use the freealut package instead. And so do I.
Erik ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
