3 ms·
However, CMake sucks in terms of installation paths. Ever tried installing a library into a libdir other than ${prefix}/lib? In the worst case, the developer tr
by matthiasv 13y ago
However, CMake sucks in terms of installation paths. Ever tried installing a library into a libdir other than ${prefix}/lib? In the worst case, the developer tries to "fix" this by guessing the architecture and append a magical 64. This works on some distributions but of course not all of them.
I got sick and tired of this situation and wrote a small CMake module [1] that accepts standard configure options to determine the installation path.
[1] http://bloerg.net/2013/10/29/turning-cmake-into-a-good-unix-citizen.html http://bloerg.net/2013/10/29/turning-cmake-into-a-good-unix-...
- leif 13y agoFor other cmake writers out there, this isn't hard. set(LIBDIR lib CACHE STRING "lib dir") install(${lib_targets} DESTINATION ${LIBDIR}) That's what I do and I am able to build packages with it just fine, that send the libs to wherever the hell they want them.
- matthiasv 13y agoI am not saying it is hard, I just wanted to point out that CMake does not provide something like this out of the box. Quite the contrary, now every developer has to re-invent this tiny wheel, and I've seen this going wrong several times.