Discussion:
openal build with / without debug symbols
Philipp Kraus
2012-09-19 00:42:23 UTC
Permalink
Hello,

I have build OpenAL under Visual Studio, it works, but I have checked
the OpenAL32.dll and I have found out the it is linked again the
MSVCR100D.dll, so it is used the debug symbols. How can I build OpenAL
without any debug symbols?
OpenAL must be linked to the MSVCR100.DLL only

Thanks

Phil
Chris Robinson
2012-09-19 04:28:01 UTC
Permalink
Post by Philipp Kraus
Hello,
I have build OpenAL under Visual Studio, it works, but I have checked
the OpenAL32.dll and I have found out the it is linked again the
MSVCR100D.dll, so it is used the debug symbols. How can I build OpenAL
without any debug symbols?
OpenAL must be linked to the MSVCR100.DLL only
Which OpenAL? OpenAL Soft, or Creative's Windows version?

If it's Creative's, I don't know. The code for their version on the SVN
server is old and hasn't been updated in a long time.

For OpenAL Soft, you'd need to set CMAKE_BUILD_TYPE to "Release"
(without quotes). If you're using one of CMake's GUIs, that setting
should be visible for you to change, then reconfigure. If you're using
cmake from the command line, then pass -DCMAKE_BUILD_TYPE=Release as a
parameter.

Hope that helps. :)
Philipp Kraus
2012-09-19 10:19:19 UTC
Permalink
Post by Chris Robinson
Post by Philipp Kraus
Hello,
I have build OpenAL under Visual Studio, it works, but I have checked
the OpenAL32.dll and I have found out the it is linked again the
MSVCR100D.dll, so it is used the debug symbols. How can I build OpenAL
without any debug symbols?
OpenAL must be linked to the MSVCR100.DLL only
Which OpenAL? OpenAL Soft, or Creative's Windows version?
I use the 1.14 version (from the git rep)
Post by Chris Robinson
If it's Creative's, I don't know. The code for their version on the SVN
server is old and hasn't been updated in a long time.
For OpenAL Soft, you'd need to set CMAKE_BUILD_TYPE to "Release"
(without quotes). If you're using one of CMake's GUIs, that setting
should be visible for you to change, then reconfigure. If you're using
cmake from the command line, then pass -DCMAKE_BUILD_TYPE=Release as a
parameter.
Hope that helps. :)
I use the command cmake -DCMAKE_BUILD_TYPE=.... -DCMAKE_INSTALL_PREFIX=....

But the OpenAL32.dll is linked to the MSVCR100D.dll if the buildtype is
set to release

Phil
Jason Daly
2012-09-19 14:55:37 UTC
Permalink
Post by Philipp Kraus
Hello,
I have build OpenAL under Visual Studio, it works, but I have checked
the OpenAL32.dll and I have found out the it is linked again the
MSVCR100D.dll, so it is used the debug symbols. How can I build OpenAL
without any debug symbols?
OpenAL must be linked to the MSVCR100.DLL only
Which implementation are you using?

--"J"
Jason Daly
2012-09-19 15:01:18 UTC
Permalink
Post by Jason Daly
Post by Philipp Kraus
Hello,
I have build OpenAL under Visual Studio, it works, but I have checked
the OpenAL32.dll and I have found out the it is linked again the
MSVCR100D.dll, so it is used the debug symbols. How can I build OpenAL
without any debug symbols?
OpenAL must be linked to the MSVCR100.DLL only
Which implementation are you using?
Sorry, my mail client was slow, so I didn't see that this was answered
already. In theory, setting the build type to Release should be all you
need to do.

--"J"
Jason Daly
2012-09-19 22:25:56 UTC
Permalink
I have found out that I should not run the msbuild, I have changed
both msbuild commands to
devenv OpenAL.sln /build Debug|Release /Project Install
and this works, the OpenAL32.dll is on the debug option linked to the
msvcr100d.dll and on release to msvcr100.dll
Glad you got it working!

--"J"

Loading...