_BINARY_DIR is the path to the build directory of the dependency.

_SOURCE_DIR is the path to the source of the dependency.

The version is explicitly givenĬPMAddPackage( calling CPMAddPackage, the following variables are defined in the local scope, where is the name of the dependency. # An archive package from a given url with an MD5 hash provided

If an additional optional parameter SYSTEM is set to a truthy value, the SYSTEM directory property of the subdirectory added will be set to true.Ī single-argument compact syntax is also supported: If an additional optional parameter EXCLUDE_FROM_ALL is set to a truthy value, then any targets defined inside the dependency won't be built by default. GIT_TAG can also be set to a specific commit or a branch name such as master, however this isn't recommended, as such packages will only be updated when the cache is cleared. On the other hand, if VERSION hasn't been explicitly specified, CPM can automatically identify the version from the git tag in some common cases. If GIT_TAG hasn't been explicitly specified it defaults to v(VERSION), a common convention for git projects. The origin may be specified by a GIT_REPOSITORY, but other sources, such as direct URLs, are also supported.

# Origin parameters forwarded to FetchContent_Declare, see below

NAME # The unique name of the dependency (should be the exported target's name) VERSION # The minimum version of the dependency (optional, defaults to 0) OPTIONS # Configuration options passed to the dependency (optional)ĭOWNLOAD_ONLY # If set, the project is downloaded, but not configured (optional)

Cross manager download