I want to build OpenAl to have a static libray

[wassim_belhadj]

Dear list,

I must use OpenAl in a visual studio project (2005).
I want to build OpenAl to have a static libray that i will include in my
project.
I downloaded the openAl Source (openal-0.08) from OpenAl website and cmake
2.6

But i have had an error:

CMake Error: find_package could not find module FindConfigHelper.cmake or a
configuration file for package ConfigHelper.
Adjust CMAKE_MODULE_PATH to find FindConfigHelper.cmake or set
ConfigHelper_DIR to the director containing a CMake configuration file for
ConfigHelper
The file will have one of the following names:
ConfigHelperConfig.cmake
confighelper-config.cmake


How can i resolve this error ?
Is there someone who has done this?


Thanks in advance!

Best regards
wassim

[Chris Robinson]

Post by wassim_belhadj
Dear list,
I must use OpenAl in a visual studio project (2005).
I want to build OpenAl to have a static libray that i will include in my
project.
I downloaded the openAl Source (openal-0.08) from OpenAl website and cmake
2.6

OpenAL isn't really designed to be a static library (think OpenGL/Direct3D,
but for audio). As well, the OpenAL source you got isn't designed or very
well tested for Visual Studio (or Windows itself). That source is the old
Linux/Unix/cross-platform source. The only Windows source available is also
quite old, and available via SVN (the latest Windows sources are closed
source).

The best way to distribute OpenAL with your project is to package with
Creative's redistributable installer, and have it run when your app installs
(or if it's just installed by extracting, have the user run it first before
your app).

[Chris Robinson]

Is there a solution for a lib (OpenAl32.lib) which did not need DLL
(OpenAL32.dll) to work?

There isn't, unfortunately. The DLL is seperate from the app so the user can
use a specific version for their system (the dsound wrapper, a hardware
driver, an alternative implementation, etc). Static linking would prevent the
user's driver from being used. The redistributable installer, however, only
needs to be run once and won't overwrite newer/other DLLs, which is why it's
the prefered method for distributing an OpenAL app.