[Openal] OpenalSoft 1.7.411 & malformed version number on ppc G5 and i386 macbook ok

[Manolache Adrian]

Sorry for the late response, i've been kind of busy with the faculty but i'm back now with a few more questions. So here's where i'm at: i've managed to successufully integrate portaudio & openal soft in the application i'm developing. After some testing i noticed that the crash i was experiencing with OpenAL SI is gone and i can say i'm pretty happy with OpenAL - Soft.
 
At startup i see the following devices:
    PortAudio Software
    Wave File Writer
 
It works without specifying any additional devices( in  ~/.alsoftrc for instance) . In the initial phase it did not work because of a rather weird thing: it seems that the application seeks libportaudio here:
   /usr/local/lib/libportaudio.2.0.0.dylib 
   /usr/local/lib/libportaudio.2.dylib 
I wondered it may be something with the paths embedded in the frameworks. After compiling the application bundle i navigated to the main binary called EnchantedForestGame ; here's what 
  otool -L  EnchantedForestGame 
has to say:
...
@executable_path/../Frameworks/libportaudio.2.dylib (compatibility version 3.0.0, current version 3.0.0)
@executable_path/../Frameworks/libopenal.1.dylib (compatibility version 1.0.0, current version 1.0.0)
....
 
Also, moving to the Frameworks directory in the bundle i see these files - copied in a copy files phase by xcode(amongst others)
libportaudio.2.0.0.dylib  libportaudio.2.dylib libopenal.1.dylib 
 
The first is the actual binary and the second is a symlink. Again
  otool -L libportaudio.2.0.0.dylib 
says:
...
@executable_path/../Frameworks/libportaudio.2.dylib (compatibility version 3.0.0, current version 3.0.0)
...
 
I'm starting to think the neccessity of the existence of libportaudio.2.0.0.dylib  libportaudio.2.dylib in /usr/local/lib is due to some setup made when configuring compilation of the library. If this is so, how should i configure the compilation of portaudio to be able to embedd it in an application bundle so the deployment of the application should not rely on the existence of portaudio on other computers and neither to a separate phase where i would install this library in /usr/local/lib querying for su rights?
 
Another problem deals with openal-soft, When compiling my application in debug and linking everything goes fine but when i compile in release mode i receive linking errors for OpenAL specific functions like(missing): alSourceStop, alDeleteBuffers, alSource3f, alBufferData, etc. I'm wondering what am i missing here since the same libraries are used for debug and release mode. 
 
I compiled OpenAl Soft and use it in debug and release with netbeans on linux and everything works like charmed.
 
What should i do?


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://opensource.creative.com/pipermail/openal/attachments/20090410/6ec3e4e6/attachment.html