File Postfix "Tags" (such as _d for debug or _s for static) about magnum HOT 4 CLOSED

Thanks for the information, I hear about CMAKE_<CONFIG>_POSTFIX for the first time. I have a few questions, however:

• What is the exact use case? I suppose this is done so the debug, dynamic and static libraries can coexist and the user would be able to select between them when calling find_package(Magnum).
• Static and dynamic libraries are (at least on Linux and Windows, don't know about OSX) differentiated by extension (e.g. .a and .so), so they can coexist (although CMake is hardcoded to use the dynamic one by default). But the information about how the library is built is saved in magnumConfigure.h as MAGNUM_BUILD_STATIC preprocessor definiton and thus the include files for these two versions would need to be installed to separate locations to avoid conflicts anyway.
• How is the postfix handled when finding the library using find_library() (i.e. from FindMagnum.cmake)? I suppose that just find_library(Magnum) won't simply be able to find libMagnum_d_s.so. More importantly, how would the user request specific library version from find_package()? Documentation for find_library() and find_package() doesn't mention anything which would help in this case.

from magnum.

What is the exact use case? I suppose this is done so the debug, dynamic and static libraries can coexist and the user would be able to select between them when calling find_package(Magnum).

To explicitly statically link or dynamically link. And also to explicitly determine which type of binary to link to for debug and release builds.

How is the postfix handled when finding the library using find_library() (i.e. from FindMagnum.cmake)? I suppose that just find_library(Magnum) won't simply be able to find libMagnum_d_s.so. More importantly, how would the user request specific library version from find_package()? Documentation for find_library() and find_package() doesn't mention anything which would help in this case.

I'm actually not sure, but SFML does use _s and _d (or -d/-s, not sure) suffixes in it's library and it does use CMake. https://github.com/LaurentGomila/SFML/blob/master/cmake/Modules/FindSFML.cmake

from magnum.

Thanks for the SFML example, I will look into it.

from magnum.

Debug/release library distinction is done as discussed in #45. Thanks again for the SFML module, it was very helpful.

On the other hand, static/dynamic libraries cannot coexist because of the reason mentioned above (different generated include file), thus they still need to be installed to (and later found in) separate location and that is nothing the build system could possibly help with.

from magnum.