Your CMake version should be newer than your compiler. It should be newer than the libraries you are using (especially Boost). New versions work better for everyone.
If you have a built in copy of CMake, it isn't special or customized for your system. You can easily install a new one instead, either on the system level or the user level. Feel free to instruct your users here if they complain about a CMake requirement being set too high. Especially if they want < 3.1 support. Maybe even if they want CMake < 3.12 support...
You can download CMake from KitWare. This is how you'll probably get CMake if you are on Windows. It's not a bad way to get it on macOS either, but using
brew install cmake is much nicer if you use Homebrew (and you should).
~ $ wget -qO- "https://cmake.org/files/v3.12/cmake-3.12.2-Linux-x86_64.tar.gz" | tar --strip-components=1 -xz -C ~/.local
If you just want a local folder with CMake only:
~ $ mkdir -p cmake-3.12 && wget -qO- "https://cmake.org/files/v3.12/cmake-3.12.2-Linux-x86_64.tar.gz" | tar --strip-components=1 -xz -C cmake-3.12 ~ $ export PATH=`pwd`/cmake-3.12/bin:$PATH
You'll obviously want to append to the PATH every time you start a new terminal, or add it to your
.bashrc or to an LMod system.
And, if you want a system install, install to
/usr/local; this is an excellent choice in a Docker container, for example on GitLab CI. Do not try it on a non-containerized system.
docker $ wget -qO- "https://cmake.org/files/v3.12/cmake-3.12.2-Linux-x86_64.tar.gz" | tar --strip-components=1 -xz -C /usr/local
If you are on a system without wget, replace
wget -qO- with
You can also build CMake on any system, it's pretty easy, but binaries are faster.
This is also provided as an official package, maintained by the authors of CMake at KitWare. It's a rather new method, and might fail on some systems (Alpine isn't supported last I checked, but that has CMake 3.8), but works really well when it works (like on Travis CI). If you have pip (Python's package installer), you can do:
gitbook $ pip install cmake
And as long as a binary exists for your system, you'll be up-and-running almost immediately. If a binary doesn't exist, it will try to use KitWare's
scikit-build package to build, which currently can't be listed as a dependency in the packaging system, and might even require (an older) copy of CMake to build. So only use this system if binaries exist, which is most of the time.
This has the benefit of respecting your current virtual environment, as well.
Personally, on Linux, I put versions of CMake in folders, like
~/opt/cmake312, and then add them to [LMod]. See
envmodule_setup for help setting up an LMod system on macOS or Linux. It takes a bit to learn, but is a great way to manage package and compiler versions.
1. I assume this is obvious, but you are downloading and running code, which exposes you to a man in the middle attack. If you are in a critical environment, you should download the file and check the checksum. (And, no, simply doing this in two steps does not make you any safer, only a checksum is safer). ↩
2. If you don't have a
.localin your home directory, it's easy to start. Just make the folder, then add
export PATH="$HOME/.local/bin:$PATH"to your
.profilefile in your home directory. Now you can install any packages you build to