vortishow.blogg.se

Cmake include order
Cmake include order










cmake include order
  1. #CMAKE INCLUDE ORDER MANUAL#
  2. #CMAKE INCLUDE ORDER PATCH#

#CMAKE INCLUDE ORDER PATCH#

Patch version if requested, else 0 PACKAGE_FIND_VERSION_TWEAK Minor version if requested, else 0 PACKAGE_FIND_VERSION_PATCH Major version if requested, else 0 PACKAGE_FIND_VERSION_MINOR When the find_package() command loads a version file it first sets theįull requested version string PACKAGE_FIND_VERSION_MAJOR lib/cmake/bar-4.2/BarConfigVersion.cmakeĪre each pairs of package configuration files and corresponding package version Package Configuration File ¶Ĭonsider a project Foo that installs the following files: Optionally a Package Version File provided with the project distribution.

#CMAKE INCLUDE ORDER MANUAL#

See the cmake-developer(7) manual for more information about creatingĪ config-file package consists of a Package Configuration File and Similarly there is no _DIR variable,īut each of the artifacts such as library locations and header file locations ItĬan still be expected to be set by convention however and should be set by Variable is not automatically set by the find_package() command. Of reference identifies the package as being found, so the _FOUND Unlike the case of an upstream-provided package configuration file, no single point Unlike a package configurationįile, it is not shipped with upstream, but is used by downstream to find theįiles by guessing locations of files with platform-specific hints. Is needed when the upstream is not built with CMake, or is not CMake-awareĮnough to otherwise provide a package configuration file. Find-module Packages ¶Ī find module is a file with a set of rules for finding the required pieces ofĪ dependency, primarily header files and libraries. The _DIR cache variable is set to the location of the Variable is set to true or false, depending on whether the package wasįound. Provided to assist downstreams in using the package.Ī set of variables which provide package status information are also setĪutomatically when using a config-file package. Packages, that is, they belong with the header files and any other files

cmake include order

The most simple way forĪ CMake user to tell cmake(1) to search in a non-standard prefix forĪ package is to set the CMAKE_PREFIX_PATH cache variable.Ĭonfig-file packages are provided by upstream vendors as part of development CMake searches in a number of locations for package configuration files, asĭescribed in the find_package() documentation. TRUE, the package will not be searched, and will alwaysĬMAKE_REQUIRE_FIND_PACKAGE_ to TRUE will make theĪ config-file package is a set of files provided by upstreams for downstreams

cmake include order

Handling of COMPONENTS and OPTIONAL_COMPONENTS is defined by theīy setting the CMAKE_DISABLE_FIND_PACKAGE_ variable to

cmake include order

In all cases, the basic formįind_package( Qt5 5.1.0 COMPONENTS Widgets OPTIONAL_COMPONENTS Xml Sql ) Indirect support for pkg-config packages is also provided via Using Packages ¶ĬMake provides direct support for two forms of packages,Ĭonfig-file Packages and Find-module Packages. Using find_package() is either a set of IMPORTED targets, orĪ set of variables corresponding to build-relevant information. PackagesĪre found with the find_package() command. Packages provide dependency information to CMake based buildsystems. Creating a Package Configuration File for the Build Tree












Cmake include order