f313f9c117
This is rather ugly, but it's necessary to get a proper export configuration. The issue was that the main OpenAL target library name is set to soft_oal when the router is being built, which is incorrect for the exported config library. Exporting the router would have the incorrect name of OpenAL::Router. So this change has the router use the OpenAL target name when it's built, which is good since it will have the standard OpenAL lib name for apps to link to and get the OpenAL::OpenAL export name. The main library's target name is changed in this case to avoid conflicts.
Source Install ============== To install OpenAL Soft, use your favorite shell to go into the build/ directory, and run: cmake .. Assuming configuration went well, you can then build it, typically using GNU Make (KDevelop, MSVC, and others are possible depending on your system setup and CMake configuration). Please Note: Double check that the appropriate backends were detected. Often, complaints of no sound, crashing, and missing devices can be solved by making sure the correct backends are being used. CMake's output will identify which backends were enabled. For most systems, you will likely want to make sure ALSA, OSS, and PulseAudio were detected (if your target system uses them). For Windows, make sure DirectSound was detected. Utilities ========= The source package comes with an informational utility, openal-info, and is built by default. It prints out information provided by the ALC and AL sub- systems, including discovered devices, version information, and extensions. Configuration ============= OpenAL Soft can be configured on a per-user and per-system basis. This allows users and sysadmins to control information provided to applications, as well as application-agnostic behavior of the library. See alsoftrc.sample for available settings. Acknowledgements ================ Special thanks go to: Creative Labs for the original source code this is based off of. Christopher Fitzgerald for the current reverb effect implementation, and helping with the low-pass and HRTF filters. Christian Borss for the 3D panning code previous versions used as a base. Ben Davis for the idea behind a previous version of the click-removal code. Richard Furse for helping with my understanding of Ambisonics that is used by the various parts of the library.