If you’re like me, when you download a project and want to build it the first thing you do is look for a configure script (or maybe ./autogen.sh if you are building from git). Lots of times I don’t bother reading the INSTALL file, or even the README. Most of the time this works out well, but sometimes there is no such file. When that happens, more often than not there is a CMakeLists.txt, which means the project uses CMake for its build system.
The realization that that the project uses CMake is, at least for me, quickly followed by a sense of disappointment. It’s not that I mind that a project is using CMake instead of Autotools; they both suck, as do all the other build systems I’m aware of. Mostly it’s just that CMake is different and, for someone who just wants to build the project, not in a good way.
First you have to remember what arguments to pass to CMake. For people who haven’t built many projects with CMake before this often involves having to actually RTFM (the horrors!), or a consultation with Google. Of course, the project may or may not have good documentation, and there is much less consistency regarding which flags you need to pass to CMake than with Autotools, so this step can be a bit more cumbersome than one might expect, even for those familiar with CMake.
After you figure out what arguments you need to type, you need to actually type them. CMake has you define variables using
-DVAR=VAL for everything, so you end up with things like
-DCMAKE_INSTALL_PREFIX=/opt/gnome instead of
--prefix=/opt/gnome. Sure, it’s not the worst thing imaginable, but let’s be honest—it’s ugly, and awkward to type.
Enter configure-cmake, a bash script that you drop into your project (as configure) which takes most of the arguments configure scripts typically accept, converts them to CMake’s particular style of insanity, and invokes CMake for you. For example,
./configure --prefix=/opt/gnome CC=clang CFLAGS="-fno-omit-frame-pointer -fsanitize=address"
Will be converted to
cmake . -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/opt/gnome -DCMAKE_INSTALL_LIBDIR=/opt/gnome/lib -DCMAKE_C_COMPILER=clang -DCMAKE_C_FLAGS="-fno-omit-frame-pointer -fsanitize=address"
Note that it assumes you’re including the GNUInstallDirs module (which ships with CMake, and you should probably be using). Other than that, the only thing which may be somewhat contentious is that it adds
-DCMAKE_BUILD_TYPE=Debug—Autotools usually builds with debugging symbols enabled and lets the package manager take care of stripping them, but CMake doesn’t. Unfortunately some projects use the build type to determine other things (like defining NDEBUG), so you can get configure-cmake to pass “Release” for the build type by passing it <code>–disable-debug</code>, one of two arguments that don’t mirror something from Autotools.
Sometimes you’ll want to be able to pass non-standard argument to CMake, which is where the other argument that doesn’t mirror something from Autotools comes in;
--passthrough also work), which just tells configure-cmake to pass all subsequent arguments to CMake untouched. For example:
./configure --prefix=/opt/gnome --pass-thru -DENABLE_AWESOMENESS=yes
Of course none of this replaces anything CMake is doing, so people who want to keep calling
cmake directly can.
So, if you maintain a CMake project, please consider dropping the configure script from configure-cmake into your project. Or write your own, or hack what I’ve done into pieces and use that, or really anything other than asking people to type those horrible CMake invocations manually.