Installer cmake avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt

Commandes et alias

• ccmake
• cmake
• cpack
• ctest

Historique du projet

The official CMake history says CMake was created in 2000 for the National Library of Medicine's Insight Toolkit, after Bill Hoffman concluded that a new portable C++ build tool was needed. The early design goals were native build-tool support, one input file across platforms, bootstrap portability with only a C++ compiler, and code-generator support.

Historique d'adoption

CMake moved from ITK into VTK and ParaView in 2002, then into major open source projects over time. The official timeline highlights KDE switching in 2006, LLVM removing autoconf in favor of CMake in 2016, Visual Studio adding integrated CMake project support in 2017, and Qt switching to CMake in 2019. The CMake about page claims more than two million downloads per month, and the batch input lists packages across Homebrew, Debian, Fedora, Arch, Nix, MacPorts, Windows package managers, and more.

Modes d'utilisation

The cmake executable generates project buildsystems, builds and installs projects, runs scripts, runs command-line helper actions, and exposes help. CMake projects begin from CMakeLists.txt files; modern workflows may also use CMakePresets.json and CMakeUserPresets.json, while generated build trees contain CMakeCache.txt.

Pourquoi les passionnés de paquets s'y intéressent

CMake is package-nerd infrastructure: it is the build-system front door for thousands of upstream projects and distro recipes. Its generator model lets package maintainers target Make, Ninja, IDE projects, and platform-native tooling from the same upstream metadata, while CTest and CPack standardize test and packaging hooks.

Chronologie

• 2000: CMake is created for the National Library of Medicine's Insight Toolkit project.
• 2002: VTK and ParaView replace their build systems with CMake.
• 2006: KDE switches to CMake, helping drive Linux distribution availability.
• 2011: Ninja generator is added to CMake.
• 2016: LLVM switches to CMake and removes autoconf.
• 2017: Microsoft Visual Studio introduces integrated support for CMake projects.
• 2019: The Qt Group switches to CMake.
• 2020: CMake Presets are incorporated into Visual Studio and Ninja Multi-Config is added.
• 2022: CMake is publicly described as the standard build system in a C++Now talk cited by the official timeline.

Related projects

• The official timeline ties CMake to ITK, VTK, ParaView, KDE, LLVM, Visual Studio, Qt, Ninja, CTest, CPack, and C++20 modules work. It is also the build dependency for projects such as cmark.

Sources

• https://cmake.org/history/
• https://cmake.org/about/
• https://cmake.org/cmake/help/latest/manual/cmake.1.html
• https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html