Get the Software
Visual Studio Code is a lightweight, cross-platform development environment that runs on Windows, Mac, and Linux systems. The Microsoft C/C for Visual Studio Code extension supports IntelliSense, debugging, code formatting, auto-completion. Visual Studio IDE Visual Studio for Mac Visual Studio Code To continue downloading, click here Download Older Visual Studio Software Visual Studio 2020-10-13T15:02:03-07:00.
You can either download binaries or source code archives for the latest stable or previous release or access the current development (aka nightly) distribution through Git. This software may not be exported in violation of any U.S. export laws or regulations. For more information regarding Export Control matters please go to https://www.kitware.com/legal.
Stay updated
Kitware provides training sessions on CMake on a regular basis. If you are interested, please register. Kitware provides support for your CMake project such as migration from other tools to CMake, auditing of existing CMake-based project and training. You can always contact kitware for more information regarding CMake. If you want to get regular updates or more information regarding CMake services please leave us your email:
Msvc For Mac Installer
![Acca Acca](/uploads/1/1/9/5/119550713/593295448.jpg)
Release Candidate (3.19.0-rc1)
The release was packaged with CPack which is included as part of the release. The .sh files are self extracting gziped tar files. To install a .sh file, run it with /bin/sh and follow the directions. The OS-machine.tar.gz files are gziped tar files of the install tree. The OS-machine.tar.Z files are compressed tar files of the install tree. The tar file distributions can be untared in any directory. They are prefixed by the version of CMake. For example, the Linux-x86_64 tar file is all under the directory cmake–Linux-x86_64. This prefix can be removed as long as the share, bin, man and doc directories are moved relative to each other. To build the source distributions, unpack them with zip or tar and follow the instructions in Readme.txt at the top of the source tree. See also the CMake 3.19 Release Notes.
Source distributions:
Msv Format
Platform | Files |
Unix/Linux Source (has n line feeds) | cmake-3.19.0-rc1.tar.gz |
cmake-3.19.0-rc1.tar.Z | |
Windows Source (has rn line feeds) | cmake-3.19.0-rc1.zip |
Binary distributions:
Platform | Files |
Windows win64-x64 Installer: Installer tool has changed. Uninstall CMake 3.4 or lower first! | cmake-3.19.0-rc1-win64-x64.msi |
Windows win64-x64 ZIP | cmake-3.19.0-rc1-win64-x64.zip |
Windows win32-x86 Installer: Installer tool has changed. Uninstall CMake 3.4 or lower first! | cmake-3.19.0-rc1-win32-x86.msi |
Windows win32-x86 ZIP | cmake-3.19.0-rc1-win32-x86.zip |
Mac OS X 10.7 or later | cmake-3.19.0-rc1-Darwin-x86_64.dmg |
cmake-3.19.0-rc1-Darwin-x86_64.tar.gz | |
Linux x86_64 | cmake-3.19.0-rc1-Linux-x86_64.sh |
cmake-3.19.0-rc1-Linux-x86_64.tar.gz |
Download verification:
Role | Files |
Cryptographic Hashes | cmake-3.19.0-rc1-SHA-256.txt |
PGP sig by EC8FEF3A7BFB4EDA | cmake-3.19.0-rc1-SHA-256.txt.asc |
Latest Release (3.18.4)
The release was packaged with CPack which is included as part of the release. The .sh files are self extracting gziped tar files. To install a .sh file, run it with /bin/sh and follow the directions. The OS-machine.tar.gz files are gziped tar files of the install tree. The OS-machine.tar.Z files are compressed tar files of the install tree. The tar file distributions can be untared in any directory. They are prefixed by the version of CMake. For example, the Linux-x86_64 tar file is all under the directory cmake–Linux-x86_64. This prefix can be removed as long as the share, bin, man and doc directories are moved relative to each other. To build the source distributions, unpack them with zip or tar and follow the instructions in Readme.txt at the top of the source tree. See also the CMake 3.18 Release Notes.
Source distributions:
Platform | Files |
Unix/Linux Source (has n line feeds) | cmake-3.18.4.tar.gz |
Windows Source (has rn line feeds) | cmake-3.18.4.zip |
Binary distributions:
Platform | Files |
Windows win64-x64 Installer: Installer tool has changed. Uninstall CMake 3.4 or lower first! | cmake-3.18.4-win64-x64.msi |
Windows win64-x64 ZIP | cmake-3.18.4-win64-x64.zip |
Windows win32-x86 Installer: Installer tool has changed. Uninstall CMake 3.4 or lower first! | cmake-3.18.4-win32-x86.msi |
Windows win32-x86 ZIP | cmake-3.18.4-win32-x86.zip |
Mac OS X 10.7 or later | cmake-3.18.4-Darwin-x86_64.dmg |
cmake-3.18.4-Darwin-x86_64.tar.gz | |
Linux x86_64 | cmake-3.18.4-Linux-x86_64.sh |
cmake-3.18.4-Linux-x86_64.tar.gz |
Download verification:
Role | Files |
Cryptographic Hashes | cmake-3.18.4-SHA-256.txt |
PGP sig by 2D2CEF1034921684 | cmake-3.18.4-SHA-256.txt.asc |
Previous Release (3.17.5)
The release was packaged with CPack which is included as part of the release. The .sh files are self extracting gziped tar files. To install a .sh file, run it with /bin/sh and follow the directions. The OS-machine.tar.gz files are gziped tar files of the install tree. The OS-machine.tar.Z files are compressed tar files of the install tree. The tar file distributions can be untared in any directory. They are prefixed by the version of CMake. For example, the Linux-x86_64 tar file is all under the directory cmake–Linux-x86_64. This prefix can be removed as long as the share, bin, man and doc directories are moved relative to each other. To build the source distributions, unpack them with zip or tar and follow the instructions in Readme.txt at the top of the source tree. See also the CMake 3.17 Release Notes.
Source distributions:
Platform | Files |
Unix/Linux Source (has n line feeds) | cmake-3.17.5.tar.gz |
Windows Source (has rn line feeds) | cmake-3.17.5.zip |
Binary distributions:
Platform | Files |
Windows win64-x64 Installer: Installer tool has changed. Uninstall CMake 3.4 or lower first! | cmake-3.17.5-win64-x64.msi |
Windows win64-x64 ZIP | cmake-3.17.5-win64-x64.zip |
Windows win32-x86 Installer: Installer tool has changed. Uninstall CMake 3.4 or lower first! | cmake-3.17.5-win32-x86.msi |
Windows win32-x86 ZIP | cmake-3.17.5-win32-x86.zip |
Mac OS X 10.7 or later | cmake-3.17.5-Darwin-x86_64.dmg |
cmake-3.17.5-Darwin-x86_64.tar.gz | |
Linux x86_64 | cmake-3.17.5-Linux-x86_64.sh |
cmake-3.17.5-Linux-x86_64.tar.gz |
Download verification:
Role | Files |
Cryptographic Hashes | cmake-3.17.5-SHA-256.txt |
PGP sig by 2D2CEF1034921684 | cmake-3.17.5-SHA-256.txt.asc |
Alternative Binary Releases
Host | Link |
Kitware’s Debian and Ubuntu packages | https://apt.kitware.com/ |
snap | https://snapcraft.io/cmake |
pip | https://pypi.org/project/cmake/ |
Older Releases
Host | Link |
kitware | https://cmake.org/files |
github | https://github.com/Kitware/CMake/releases |
Editor Syntax Files
Editor | Files |
emacs | cmake-mode.el |
vim | vim-cmake-syntax |
Current development distribution
Each night binaries are created as part of the testing process. Other than passing all of the tests in CMake, this version of CMake should not be expected to work in a production environment. It is being produced so that users can test bug fixes done upstream without having to build CMake.
Nightly Binaries | Link |
https | https://cmake.org/files/dev/ |
Alternatively one may build from source. Development is managed on Kitware’s GitLab instance:
On UNIX, one may use the bootstrap script provided in the source tree to build CMake. In order to build the windows version of CMake you will need a current binary installation of CMake to bootstrap the build process.
Qt Creator groups settings used for building and running projects as kits to make cross-platform and cross-configuration development easier. Each kit consists of a set of values that define one environment, such as a device, compiler, Qt version, and debugger command to use, and some metadata, such as an icon and a name for the kit. Once you have defined kits, you can select them to build and run projects.
Qt Creator supports development for the desktop and for the following types of devices:
- Boot2Qt Device (commercial only)
- Boot2Qt Emulator Device (commercial only)
- iOS Simulator
- MCU Device (commercial only)
- Windows Phone Emulator
- Windows Runtime (local)
Filtering Kit Settings
Typically, only a subset of the kit settings is relevant for a particular setup. Therefore, Qt Creator plugins register sets of relevant settings that you can view and modify in Tools > Options > Kits. For example, if you use CMake to build all your projects, you can hide Qbs and qmake settings by default.
To hide and show settings in the Kits tab for the current kit, select Settings Filter. To view and modify the settings displayed when you add a new kit, select Default Settings Filter.
Specifying Kit Settings
To add kits:
- Select Tools > Options > Kits > Add.To clone the selected kit, select Clone.
- In the Name column, enter a name for the kit.
- Select the button to select an image to use as an icon for the kit.
- In the File system name field, enter a name for the kit to use as a part of directory names. This value is used for the CurrentKit:FileSystemName variable, which determines the name of the shadow build directory, for example.
- In the Device type field, select the type of the device.Double-click the icon next to the field to select the image that is displayed in the kit selector for this kit. You can use any image in a supported file format (for example, PNG). The image is scaled to the size 64x64 pixels. For example, using the compiler logo as an icon allows you to easily see, which compiler is used to build the project for the selected kit.
- In the Device field, select a device.
- In the Sysroot field, specify the directory where the device image is located. If you are not cross-compiling, leave this field empty.
- In the Emulator skin field, select the skin to use for the Boot2Qt Emulator Device.
- In the Compiler field, select the C or C++ compiler that you use to build the project. You can add compilers to the list if they are installed on the development PC, but were not detected automatically. For more information, see Adding Compilers. This setting is used to tell the code model which compiler is used. If your project type and build tool support it, Qt Creator also tells the build tool to use this compiler for building the project.
- In the Environment field, select Change to modify environment variable values for build environments in the Edit Environment Changes dialog. For more information about how to add and remove variable values, see Batch Editing.
- Select the Force UTF-8 MSVC compiler output check box to either switch the language of MSVC to English or to keep the language setting and just force UTF-8 output, depending on the MSVC compiler used.
- In the Debugger field, select the debugger to debug the project on the target platform. Qt Creator automatically detects available debuggers and displays a suitable debugger in the field. You can add debuggers to the list. For more information, see Adding Debuggers.For Android kits, the Android GDB server field will display the path to GDB server executable.
- In the Qt version field, select the Qt version to use for building the project. You can add Qt versions to the list if they are installed on the development PC, but were not detected automatically. For more information, see Adding Qt Versions.Qt Creator checks the directories listed in the
PATH
environment variable for the qmake executable. If a qmake executable is found, it is referred to as Qt in PATH and selected as the Qt version to use for the Desktop kit that is created by default. - In the Qt mkspec field, specify the name of the mkspec configuration that should be used by qmake. If you leave this field empty, the default mkspec of the selected Qt version is used.
- In the Additional Qbs profile settings field, select Change to add settings to Qbs build profiles. For more information, see Editing Qbs Profiles.
- In the CMake Tool field, select the CMake executable to use for building the project. Select Manage to add installed CMake executables to the list. For more information, see Adding CMake Tools.
- In the CMake generator field, select Change to edit the CMake Generator to use for producing project files. Only the generators with names beginning with the string CodeBlocks produce all the necessary data for the Qt Creator code model. Qt Creator displays a warning if you select a generator that is not supported.
- In the CMake configuration field, select Change to edit the parameters of the CMake configuration for the kit.
- In the Meson tool field, select the Meson tool to use for building the project. Select Manage to add installed Meson tools to the list. For more information, see Adding Meson Tools.
- In the Ninja tool field, select the Ninja tool to use for building the project with Meson. Select Manage to add installed Ninja tools to the list.
Qt Creator uses the default kit if it does not have enough information to choose the kit to use. To set the selected kit as the default kit, select Make Default.
Using Ninja as a CMake Generator
To use Ninja with CMake, you must install it and select it as the CMake generator in the build and run kit:
- Install Ninja.
- Add the path to the Ninja executable to the value of the PATH system variable.
- Select Tools > Options > Kits, and then select the build and run kit for the project.
- Select Change next to the CMake generator field to open the CMake Generator dialog.
- In the Generator field, select Ninja.
- Select OK to return to the Kits tab.
- Select OK or Apply to save your changes.
Note: To make sure that old build artifacts don't get in the way the first time you build the project after the change, select Build > Rebuild Project. This cleans up the build directory and performs a new build.
![Msvc For Mac Msvc For Mac](/uploads/1/1/9/5/119550713/498910151.png)
Editing Qbs Profiles
To view the Qbs profile associated with the kit, select Tools > Options > Qbs > Profiles.
You can add keys and values to the profile or remove them from it, as well as modify existing values. For a list of available keys and values, see List of Modules in the Qbs Manual.
To edit the Qbs profile associated with the kit:
- Select Change next to the Additional Qbs Profile Settings field to open the Custom Properties dialog.
- Double-click an empty cell in the Key column to specify the key to add or modify as:
<module_name>.<property_name>
. - Double-click the cell on the same row in the Value column to specify a value as a JSON literal.
- Select Add to add the key-value pair.
- Click OK.
To modify an existing value, double-click it in the Value field.
To remove the selected property, select Remove.
© 2020 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.