3 ms·
cmake is standard enough now that 'magical unicorn' is rather unfair. I've had more difficulty with bare/automake makefile-based systems than with cmake (not th
by rcxdude 13y ago
cmake is standard enough now that 'magical unicorn' is rather unfair. I've had more difficulty with bare/automake makefile-based systems than with cmake (not that cmake is at all stellar: but it can at least handle spaces in filenames).
- matthiasv 13y agoHowever, 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.
- JNRowe 13y agoNot sure where the cut off is or should be, but it doesn't feel standard to me. On my anecdotal desktop install there are two packages that use cmake; awesome and taskwarrior. Grep'ing the ebuilds on this Gentoo box, shows me ~400 packages out of ~16000 that use cmake(excluding KDE where it clearly is standard). A lot of the remaining ones seem to be very project specific too(70 leechcraft, 11 fcitx, 10 opensync).
- keenerd 13y agoGrepping the PKGBUILDs on Arch looks quite a bit different Official: 547 out of 5115 use cmake. Unofficial: 5167 out of 47069 use cmake. A lot of these offer plain Makefiles too, but cmake is decently popular and hard to dismiss.
- peterwwillis 13y agoFor me it's not really about difficulty, it's about extra time. Is it going to take me extra time to find, download, install, and learn how to use your unusual build tool? If so, that sucks. Using the most standard/common build tools saves packagers headaches. Autoconf/Automake are more popular so it's going to be a lot easier on packagers if developers use them. But if they use them incorrectly, packagers will have to hack on the Makefiles when they could have run a bootstrapper like autoreconf.