From: Jari H. <ja...@fl...> - 2009-11-28 23:12:56
|
On 2009-11-28 23.01, Erik Hofman wrote: > Jari Häkkinen wrote: >> 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 Yes, you are right. Jari |