#Cmake target install#

(You can, and will, re-run CMake several times on the same binary folder.) Cache variables include user-configurable options defined by the project such as CMakeDemo’s DEMO_ENABLE_MULTISAMPLE option (explained later), and precomputed information to help speed up CMake runs. This is where cache variables are stored. It’s a single text file in the binary folder named CMakeCache.txt. You can even create several binary folders, side-by-side, that use different build systems or configuration options. A common practice is to create a subdirectory build beneath CMakeLists.txt.īy keeping the binary folder separate from the source, you can delete the binary folder at any time to get back to a clean slate. You can create the binary folder anywhere you want. The binary folder is where CMake generates the build pipeline. The source folder is the one containing CMakeLists.txt. To generate a build pipeline, CMake needs to know the source and binary folders. A build pipeline might be a Visual Studio. The Source and Binary FoldersĬMake generates build pipelines.

#Cmake target install#

You can also install it through MacPorts, Homebrew, Cygwin or MSYS2. In Unix-like environments, including Linux, it’s usually available through the system package manager. If you don’t have CMake yet, there are installers and binary distributions on the CMake website. However, I recommend reading the first two sections first. The information here applies to any CMake-based project, so feel free to skip ahead to any section.