brew / Approval Gates

cmake mit Homebrew, apk, chocolatey, apt, dnf, MacPorts, Nix, pacman, zypper, scoop, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für cmake in AI-Agent-Workflows.

Installationsbefehl Sicherheitshinweise

Agent-Sicherheit

Antwort zur Agent-Sicherheit

cmake configures native builds and can run project-defined build commands.

Credential-Zugriff

Reads environment variables, toolchain files, and project config.

Änderungen an Remote-Zustand

Usually local, but custom commands can call external services.

Publish-/Artefakt-Risiko

Can produce native release artifacts and installer packages.

Empfohlene Kontrolle

Gate install/package targets and custom commands that use secrets.

Hinweise für Agent-Nutzung

Allow configure/build in scanned worktrees; require approval for install, package, and secret-backed custom targets.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install cmake

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install cmake

MacPorts ports tree · devel/cmake/Portfile · Quelle: api.github.com

Linux

Alpine Linux apkverifiziert · 92%

sudo apk add cmake

Alpine Linux edge package indexes · cmake · Quelle: dl-cdn.alpinelinux.org

Debian aptverifiziert · 92%

sudo apt install cmake

Debian stable package indexes · cmake · Quelle: deb.debian.org

Fedora dnfverifiziert · 92%

sudo dnf install cmake

Fedora Rawhide package metadata · cmake · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%

nix profile install nixpkgs#cmake

nixpkgs package indexes · pkgs/by-name/cm/cmake/package.nix · Quelle: api.github.com

Arch Linux pacmanverifiziert · 92%

sudo pacman -S cmake

Arch Linux sync databases · cmake · Quelle: geo.mirror.pkgbuild.com

openSUSE zypperverifiziert · 92%

sudo zypper install cmake

openSUSE Tumbleweed package metadata · cmake · Quelle: download.opensuse.org

Windows

Chocolateyverifiziert · 92%

choco install cmake

Chocolatey community package catalog · cmake · Quelle: community.chocolatey.org

Scoopverifiziert · 92%

scoop install main/cmake

Scoop official bucket manifest trees · bucket/cmake.json · Quelle: api.github.com

Windows Package Managerverifiziert · 92%

winget install --id Kitware.CMake -e

Windows Package Manager source index · Kitware.CMake · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

Cross-platform make

Projektlinks

Befehle und Aliase

ccmake
cmake
cpack
ctest

Verlauf

Projektgeschichte und Nutzung

CMake is Kitware's cross-platform build, test, and package tooling family. It began as infrastructure for large portable C++ scientific software and became the de facto build-system interface for much of the C and C++ open source ecosystem.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

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.

Quellen

Approval Gates

Metadaten für menschliche Prüfung riskanter Befehle

Der lokale Approval-Gate-Seed enthält 6 Regeln für cmake. Abgedeckte Einstiegspunkte: cmake, cpack, ctest. Schweregrade: hoch, mittel. Abdeckung: partial, geprüft am 2026-05-21.

Beispiele für gated Aktionen

Execute a CMake script with -P.
Invoke the configured native build tool.
Install build outputs to a destination prefix.
Remove paths through CMake command mode.
Execute project tests.
Generate release packages or installers.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: CMakePresets.jsonCMakeUserPresets.json<build-tree>/CMakeCache.txt

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit
`ccmake`	cli	globales Executable
`cmake`	cli	globales Executable
`cpack`	cli	globales Executable
`ctest`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-10

Manager-Version4.4.0

Manager aktualisiert2026-07-10

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

https://github.com/Kitware/CMake

InfoNo cached GitHub release or tag data was available.https://github.com/Kitware/CMakenone Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:cmake
Version	4.4.0
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/cmake
Homepage	https://www.cmake.org/
Repository	https://github.com/Kitware/CMake
Upstream-Dokumentation	https://cmake.org/cmake/help/latest
Lizenz	BSD-3-Clause
Quellarchiv	https://github.com/Kitware/CMake/releases/download/v4.4.0/cmake-4.4.0.tar.gz
Zuletzt aktualisiert	2026-07-10T04:16:11Z
Pulse	updated
Von macOS bereitgestellte Bibliotheken	ncurses
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sequoia, sonoma, tahoe, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert
Einschränkungen	To install the CMake documentation, run: brew install cmake-docs

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	cmake
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt95%

cmake 3.31.6-2

cross-platform, open-source make system