Downloads:

84,705

Downloads of v 3.23.1:

1,449

Last Update:

12 Apr 2022

Package Maintainer(s):

Software Author(s):

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

Tags:

cmake compiler make build foss cross-platform

CMake (Portable)

This is not the latest version of CMake (Portable) available.

  • 1
  • 2
  • 3

3.23.1 | Updated: 12 Apr 2022

Downloads:

84,705

Downloads of v 3.23.1:

1,449

Software Author(s):

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

  • 1
  • 2
  • 3
CMake (Portable) 3.23.1

This is not the latest version of CMake (Portable) available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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

>

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

>

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

>

Deployment Method:

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

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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://community.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. Copy Your Script

choco upgrade cmake.portable -y --source="'INTERNAL REPO URL'" --version="'3.23.1'" [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.portable -y --source="'INTERNAL REPO URL'" --version="'3.23.1'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install cmake.portable
  win_chocolatey:
    name: cmake.portable
    version: '3.23.1'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'cmake.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.23.1'
end

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


cChocoPackageInstaller cmake.portable
{
    Name     = "cmake.portable"
    Version  = "3.23.1"
    Source   = "INTERNAL REPO URL"
}

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


package { 'cmake.portable':
  ensure   => '3.23.1',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. 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 as a trusted package on 12 Apr 2022.

Description

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.

Development


legal\LICENSE.txt
CMake - Cross Platform Makefile Generator
Copyright 2000-2017 Kitware, Inc. and Contributors
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

* Redistributions of source code must retain the above copyright
  notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright
  notice, this list of conditions and the following disclaimer in the
  documentation and/or other materials provided with the distribution.

* Neither the name of Kitware, Inc. nor the names of Contributors
  may be used to endorse or promote products derived from this
  software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

------------------------------------------------------------------------------

The following individuals and institutions are among the Contributors:

* Aaron C. Meadows <[email protected]>
* Adriaan de Groot <[email protected]>
* Aleksey Avdeev <[email protected]>
* Alexander Neundorf <[email protected]>
* Alexander Smorkalov <[email protected]>
* Alexey Sokolov <[email protected]>
* Alex Turbov <[email protected]>
* Andreas Pakulat <[email protected]>
* Andreas Schneider <[email protected]>
* André Rigland Brodtkorb <[email protected]>
* Axel Huebl, Helmholtz-Zentrum Dresden - Rossendorf
* Benjamin Eikel
* Bjoern Ricks <[email protected]>
* Brad Hards <[email protected]>
* Christopher Harvey
* Christoph Grüninger <[email protected]>
* Clement Creusot <[email protected]>
* Daniel Blezek <[email protected]>
* Daniel Pfeifer <[email protected]>
* Enrico Scholz <[email protected]>
* Eran Ifrah <[email protected]>
* Esben Mose Hansen, Ange Optimization ApS
* Geoffrey Viola <[email protected]>
* Google Inc
* Gregor Jasny
* Helio Chissini de Castro <[email protected]>
* Ilya Lavrenov <[email protected]>
* Insight Software Consortium <insightsoftwareconsortium.org>
* Jan Woetzel
* Kelly Thompson <[email protected]>
* Konstantin Podsvirov <[email protected]>
* Mario Bensi <[email protected]>
* Mathieu Malaterre <[email protected]>
* Matthaeus G. Chajdas
* Matthias Kretz <[email protected]>
* Matthias Maennich <[email protected]>
* Michael Stürmer
* Miguel A. Figueroa-Villanueva
* Mike Jackson
* Mike McQuaid <[email protected]>
* Nicolas Bock <[email protected]>
* Nicolas Despres <[email protected]>
* Nikita Krupen'ko <[email protected]>
* NVIDIA Corporation <www.nvidia.com>
* OpenGamma Ltd. <opengamma.com>
* Per Øyvind Karlsen <[email protected]>
* Peter Collingbourne <[email protected]>
* Petr Gotthard <[email protected]>
* Philip Lowman <[email protected]>
* Philippe Proulx <[email protected]>
* Raffi Enficiaud, Max Planck Society
* Raumfeld <raumfeld.com>
* Roger Leigh <[email protected]>
* Rolf Eike Beer <[email protected]>
* Roman Donchenko <[email protected]>
* Roman Kharitonov <[email protected]>
* Ruslan Baratov
* Sebastian Holtermann <[email protected]>
* Stephen Kelly <[email protected]>
* Sylvain Joubert <[email protected]>
* Thomas Sondergaard <[email protected]>
* Tobias Hunger <[email protected]>
* Todd Gamblin <[email protected]>
* Tristan Carel
* University of Dundee
* Vadim Zhukov
* Will Dicharry <[email protected]>

See version control history for details of individual contributions.

The above copyright and license notice applies to distributions of
CMake in source and binary form.  Third-party software packages supplied
with CMake under compatible licenses provide their own copyright notices
documented in corresponding subdirectories or source files.

------------------------------------------------------------------------------

CMake was initially developed by Kitware with the following sponsorship:

 * National Library of Medicine at the National Institutes of Health
   as part of the Insight Segmentation and Registration Toolkit (ITK).

 * US National Labs (Los Alamos, Livermore, Sandia) ASC Parallel
   Visualization Initiative.

 * National Alliance for Medical Image Computing (NAMIC) is funded by the
   National Institutes of Health through the NIH Roadmap for Medical Research,
   Grant U54 EB005149.

 * Kitware, Inc.
legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <https://cmake.org/download/>
and can be verified by doing the following:

1. Download the following:
  32-Bit software: <https://github.com/Kitware/CMake/releases/download/v3.23.1/cmake-3.23.1-windows-i386.zip>
  64-Bit software: <https://github.com/Kitware/CMake/releases/download/v3.23.1/cmake-3.23.1-windows-x86_64.zip>
2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:

  checksum type: sha256
  checksum32: DB5860CBE101A1029676F62E158ED2F25390D52DDD47199AE53EA11FE0374908
  checksum64: 9B509CC4EB7191DC128CFA3F2170036F9CBC7D9D5F93FF7FAFC5B2D77B3B40DC

The file 'LICENSE.txt' has been obtained from <https://gitlab.kitware.com/cmake/cmake/blob/master/Copyright.txt>
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path -parent $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName = $env:ChocolateyPackageName
  file        = "$toolsPath\cmake-3.23.1-windows-i386.zip"
  file64      = "$toolsPath\cmake-3.23.1-windows-x86_64.zip"
  destination = $toolsPath
}

Get-ChocolateyUnzip @packageArgs
Remove-Item $toolsPath\*.zip -ea 0
tools\cmake-3.23.1-windows-i386.zip
md5: A9CE386727900ED7EB3CF5712EF61FB6 | sha1: 719BCE22BF524DD0177A24A717A247C77565105C | sha256: DB5860CBE101A1029676F62E158ED2F25390D52DDD47199AE53EA11FE0374908 | sha512: E61B02D1884F2EA9F4C049C4671E3185EB158D88FD8033A9607A9D231DE43C2813766798317E72F3A2A4BA3A587F36CA37BA7A35D01E1FC3C3360E09951347F2
tools\cmake-3.23.1-windows-x86_64.zip
md5: 15752C2E37C764821BBF72E94B4FC81A | sha1: 2FF10C6ECFB21116EBDE124AF1EF8EE7B0F1F94E | sha256: 9B509CC4EB7191DC128CFA3F2170036F9CBC7D9D5F93FF7FAFC5B2D77B3B40DC | sha512: 89192C9BF9DFA80FF55A280BA5C6253FC11B4967341807A879A47609997CA1D13121E57C0E90373ADC7FC10D013E49E8FC309413DC8F8641A820E463EF2985AB

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.

Add to Builder Version Downloads Last Updated Status
CMake (Portable) 3.24.0-rc5 12 Friday, July 29, 2022 Approved
CMake (Portable) 3.24.0-rc4 17 Wednesday, July 20, 2022 Approved
CMake (Portable) 3.24.0-rc3 19 Thursday, July 7, 2022 Approved
CMake (Portable) 3.24.0-rc2 22 Friday, June 24, 2022 Approved
CMake (Portable) 3.24.0-rc1 25 Wednesday, June 15, 2022 Approved
CMake (Portable) 3.23.3 223 Friday, July 29, 2022 Approved
CMake (Portable) 3.23.2 1736 Thursday, May 26, 2022 Approved
CMake (Portable) 3.23.1 1449 Tuesday, April 12, 2022 Approved
CMake (Portable) 3.23.0 307 Tuesday, March 29, 2022 Approved

Discussion for the CMake (Portable) Package

Ground Rules:

  • This discussion is only about CMake (Portable) and the CMake (Portable) 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 (Portable), 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