Downloads of v 3.22.0-rc1:


Last Update:

14 Oct 2021

Package Maintainer(s):

Software Author(s):

  • Andy Cedilnik
  • Bill Hoffman
  • Brad King
  • Ken Martin
  • Alexander Neundorf


cmake compiler make build foss cross-platform


This is a prerelease version of CMake.

  • 1
  • 2
  • 3

3.22.0-rc1 | Updated: 14 Oct 2021



Downloads of v 3.22.0-rc1:


Software Author(s):

  • Andy Cedilnik
  • Bill Hoffman
  • Brad King
  • Ken Martin
  • Alexander Neundorf

  • 1
  • 2
  • 3
CMake 3.22.0-rc1

This is a prerelease version of CMake.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


To install CMake, run the following command from the command line or from PowerShell:


To upgrade CMake, run the following command from the command line or from PowerShell:


To uninstall CMake, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade cmake -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade cmake -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure cmake installed
    name: cmake
    state: present
    version: 3.22.0-rc1
    source: STEP 3 URL

See docs at

chocolatey_package 'cmake' do
  action    :install
  version  '3.22.0-rc1'
  source   'STEP 3 URL'

See docs at

    Name: cmake,
    Version: 3.22.0-rc1,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller cmake
   Name     = 'cmake'
   Ensure   = 'Present'
   Version  = '3.22.0-rc1'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'cmake':
  provider => 'chocolatey',
  ensure   => '3.22.0-rc1',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install cmake version="3.22.0-rc1" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.

CMake is an open-source, cross-platform family of tools designed to build, test and package software. CMake is used to control the software compilation process using simple platform and compiler independent configuration files, and generate native makefiles and workspaces that can be used in the compiler environment of your choice. The suite of CMake tools were created by Kitware in response to the need for a powerful, cross-platform build environment for open-source projects such as ITK and VTK.


MSI Properties


  • None - Do not add CMake to PATH (default)
  • System - Add CMake to system PATH for all users
  • User - Add CMake to PATH for the current user


  • 0 = Do not create desktop icon (default)
  • 1 = Create CMake desktop icon


  • 0 = Install for the current user only
  • 1 = Install for all users (default)

For example: choco install cmake --installargs 'ADD_CMAKE_TO_PATH=System'

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
CMake 3.22.0-rc1 50 Thursday, October 14, 2021 Exempted
CMake 3.21.2 15847 Wednesday, August 25, 2021 Approved
CMake 3.21.0 25086 Wednesday, July 14, 2021 Approved
CMake 3.21.0-rc3 77 Thursday, July 8, 2021 Exempted
CMake 3.21.0-rc2 177 Wednesday, June 30, 2021 Exempted
CMake 3.21.0-rc1 178 Wednesday, June 23, 2021 Exempted
CMake 3.20.6 15 Monday, September 20, 2021 Approved
CMake 3.20.5 14511 Monday, June 21, 2021 Approved

Discussion for the CMake Package

Ground Rules:

  • This discussion is only about CMake and the CMake package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or CMake, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus