| How do I compile OpenAL from CVS? |
|
| Written by Jonas | |||||
| Tuesday, 10 January 2006 | |||||
Page 2 of 3 Compiling OpenAL Aftern downloading has (hopefully) succeeded, the first step will be to compile OpenAL: $ cd portableThis is quite likely to produce a lot of warning messages, but in the end you should have a new file configure in the current directory. It is used to specify compilation options. This is what I used: $ CFLAGS="-O2 -g -mmmx" ./configure --disable-shared --enable-static --enable-sdl --enable-alsa --disable-arts --disable-bsd --disable-esd --disable-irix --enable-linux --disable-morphos --disable-solaris --disable-windows --disable-mp3 --disable-vorbisIt is important to include the -mmmx flag (yes, that's 3 'm's) when compiling for PCs. Else, OpenAL might be built without special optimizations and you'll experience slowdowns when many sound sources are audible. The configure script generates a bunch of Makefiles for us, so we can start compilation the usual way: $ makeAs we were building a static version of the OpenAL library, there is no need to do make install afterwards. To get it included in a Thunder&Lightning build, you just pass the library's path (portable/src/.libs/libopenal.so) as the argument of --with-openal-libs to Thunder&Lightning's configure script. |
|||||
| Last Updated ( Wednesday, 22 August 2007 ) | |||||