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 3.28+ support...
Quick list (more info on each method below)
Ordered by author preference:
You can download CMake from KitWare. This is how you will probably get CMake if you are on Windows. It's not a bad way to get it on macOS either (and a Universal2 version is supplied supporting both Intel and Apple Silicon), but using
brew install cmake is much nicer if you use Homebrew (and you should; Apple even supports Homebrew such as during the Apple Silicon rollout). You can also get it on most other package managers, such as Chocolatey for Windows or MacPorts for macOS.
On Linux, there are several options. Kitware provides a Debian/Ubuntu apt repository, as well as snap packages. There are universal Linux binaries provided, but you'll need to pick an install location. If you already use
~/.local for user-space packages, the following single line command1 will get CMake for you 2:
~ $ wget -qO- "https://cmake.org/files/v3.28/cmake-3.28.3-linux-x86_64.tar.gz" | tar --strip-components=1 -xz -C ~/.local
The names changed in 3.20; older releases had names like
cmake-3.19.7-Linux-x86_64.tar.gz. If you just want a local folder with CMake only:
~ $ mkdir -p cmake-3.28 && wget -qO- "https://cmake.org/files/v3.28/cmake-3.28.3-linux-x86_64.tar.gz" | tar --strip-components=1 -xz -C cmake-3.28 ~ $ export PATH=`pwd`/cmake-3.28/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.28/cmake-3.28.3-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.
CMake Default Versions
Here are some common build environments and the CMake version you'll find on them. Feel free to install CMake yourself, it's 1-2 lines and there's nothing "special" about the built in version. It's also very backward compatible.
Also Scoop is generally up to date. The normal installers from CMake.org are common on Windows, too.
Homebrew is quite a bit more popular nowadays on macOS, at least according to Google Trends.
The default on 8 is not too bad, but you should not use the default on 7. Use the EPEL package instead.
You should only use the default CMake on 18.04+; it's an LTS release with a pretty decent minimum version!
pip install cmake on many systems. Add
--user if you have to (modern pip does this for you if needed). This does not supply Universal2 wheels yet.
|Mid November 2018 this image became ready for widescale use.
|Same as Xenial at the moment.
|kept up to date
|GitHub Actions 20.04
|Same runners as Azure DevOps
If you are using GitHub Actions, also see the jwlawson/actions-setup-cmake action, which can install your selection of CMake, even in a docker action run.
Versions less than 3.10 are marked by a deeper color of red.
Also see pkgs.org/download/cmake.
This is also provided as an official package, maintained by the authors of CMake at KitWare and several PyPA members, including myself. It's now supported on special architectures, like PowerPC on Linux and Apple Silicon on macOS, and on MUSL systems like Alpine too. 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, and will 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. It really shines when placed in a
pyproject.toml file, however - it will only be installed to build your package, and will not remain afterwards! Fantastic.
This also, of course, works with pipx. So you can even use
pipx run cmake to run CMake in a disposable virtual environment, without any setup - and this works out-of-the-box on GitHub Actions, since
pipx is a supported package manager there!
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