#CMAKE SET VARIABLE SOFTWARE#
#CMAKE SET VARIABLE CODE#

Every CMakeLists.txt file need not define a project, but one reason to define a project is to create this variable so you can refer to its binary files later, in other CMakeLists.txt files.

This is the directory in the build tree that corresponds to the CMakeLists.txt file that contains a project( projectName) definition. projectName_BINARY_DIR: Binary directory for the named project.

Not every CMakeLists.txt file defines a projectвЂ“this is the directory in the build tree that corresponds to the most recent CMakeLists.txt file that defined a project.

PROJECT_BINARY_DIR: Top level binary directory for the current project.

The path to the generated source file is appended to the srcvar variable. This variable contains that subdirectory. This category includes CMake utility functions for external projects. When an add_subdirectory command is encountered in a CMakeLists.txt file, a corresponding directory is created in the build directory.

CMAKE_CURRENT_BINARY_DIR: The path to the binary directory currently being processed.

This is the directory in which you ran the cmake command.

CMAKE_BINARY_DIR: The path to the top level of the build tree.

Each of the following variables refers to a directory in the build tree corresponding to a source tree directory that contains a CMakeLists.txt file. The build tree will contain a directory hierarchy corresponding to the hierarchy of directories in the source tree containing CMakeLists.txt files. Every CMakeLists.txt file need not define a project, but one reason to define a project is to create this variable so you can refer to its source files later, in other CMakeLists.txt files. This is the directory that contains the CMakeLists.txt file that contains the project( projectName) definition.

projectName_SOURCE_DIR: Source directory for the named project.

Not every CMakeLists.txt file defines a projectвЂ“this is the directory that contains the most recent CMakeLists.txt file that defined a project.

PROJECT_SOURCE_DIR: Top level source directory for the current project.

CMAKE_CURRENT_SOURCE_DIR: The path to the directory containing the CMakeLists.txt file that is currently being processed.

That is, this is the source directory you specify to the cmake command. This is the directory that contains the top-level CMakeLists.txt file.

You can change the value of these variables in your CMakeLists.txt to modify the behavior of CMake for your project. A list of common variables used internally by CMake can be seen here.

CMAKE_SOURCE_DIR: The path to the top level of the source tree. To list all the variables that are defined and their current values, try this in a directory that has a CMakeLists.txt file: cmake -LAH.

Note how every one of them refers to a directory that contains a CMakeLists.txt file.

#CMAKE SET VARIABLE CODE#

These variables contain the paths to various source code directories. As its name suggests, add_subdirectory also creates a directory in the build tree. These sub-control files are executed using the add_subdirectory command. While a simple CMake project will have only a single CMakeLists.txt control file, larger projects will contain a hierarchy of CMakeLists.txt files, each in its own directory. Thus in CMake there are two sets of variables that refer to directories: one for the source code, and another for the binary code. This means that when you build, you create a separate directory (folder), and build there, not in the same directory that contains the source code. With CMake, you generally do out of source builds. If you have an better (or more correct) explanation, please leave a comment. I wrote my understanding of these variables to help myself remember, and I will share it with you. I found the relationship between certain groups of related CMake variables troublesome. You create the CMake control file once and based on this file, CMake will create almost any build environment for you: GNU Make for Linux, Eclipse project, Visual Studio solution for Windows, and the list goes on. You are allowed to change the value of these variables in your CMakeLists.txt. These have default values or values that are based on your project environment. CMake uses many variables that are officially documented.

#CMAKE SET VARIABLE SOFTWARE#

Cloud build default environment variables.CMake creates software build systems for a wide variety of platforms based on a single, unified control fileвЂ“itвЂ™s a makefile maker. 2014-Feb-14 Ashwin Nanjappa cmake, variable Archive.

Cmake set variable