Downloads:

496,255

Downloads of v 3.2.3:

4,207

Last Update:

02 Jun 2015

Package Maintainer(s):

Software Author(s):

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

Tags:

compiler make build

CMake

This is not the latest version of CMake available.

3.2.3 | Updated: 02 Jun 2015

Downloads:

496,255

Downloads of v 3.2.3:

4,207

Maintainer(s):

Software Author(s):

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

Tags:

compiler make build

CMake 3.2.3

This is not the latest version of CMake available.

All Checks are Unknown

2 Test of Unknown Status

Hide Checks
Hide Checks

Validation Testing Unknown

Verification Testing Unknown

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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

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'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Ensure cmake installed
  win_chocolatey:
    name: cmake
    state: present
    version: 3.2.3
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'cmake' do
  action    :install
  version  '3.2.3'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: cmake,
    Version: 3.2.3,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller cmake
{
   Name     = 'cmake'
   Ensure   = 'Present'
   Version  = '3.2.3'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'cmake':
  provider => 'chocolatey',
  ensure   => '3.2.3',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install cmake version="3.2.3" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

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 was approved by moderator ferventcoder on 03 Jun 2015.

Description

CMake is a 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. CMake generates native makefiles and workspaces that can be used in the compiler environment of your choice.

Documentation
Development
Source code

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.17.3 2174 Thursday, May 28, 2020 Approved
CMake 3.17.2 20771 Tuesday, April 28, 2020 Approved
CMake 3.17.1 11827 Thursday, April 9, 2020 Approved
CMake 3.17.0 10650 Friday, March 20, 2020 Approved
CMake 3.17.0-rc3 76 Thursday, March 12, 2020 Exempted
CMake 3.17.0-rc2 88 Tuesday, March 3, 2020 Exempted
CMake 3.16.8 4 Monday, June 1, 2020 Approved
CMake 3.16.7 18 Wednesday, May 27, 2020 Approved
CMake 3.16.6 161 Friday, April 10, 2020 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