[Cmake-commits] [cmake-commits] hoffman committed Download.html 1.6 1.7 cmake-2-6.html 1.2 1.3 ctest-2-6.html 1.2 1.3 index.html 1.15 1.16
cmake-commits at cmake.org
cmake-commits at cmake.org
Fri Aug 1 12:50:31 EDT 2008
Update of /cvsroot/CMake/CMakeWeb/HTML
In directory public:/mounts/ram/cvs-serv17415
Modified Files:
Download.html cmake-2-6.html ctest-2-6.html index.html
Log Message:
ENH: 2.6.1 cmake
Index: cmake-2-6.html
===================================================================
RCS file: /cvsroot/CMake/CMakeWeb/HTML/cmake-2-6.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C 2 -d -r1.2 -r1.3
*** cmake-2-6.html 6 May 2008 14:50:34 -0000 1.2
--- cmake-2-6.html 1 Aug 2008 16:50:29 -0000 1.3
***************
*** 43,47 ****
<h2><a name="section_Options"/>Options</h2>
<ul>
! <li><a href="#opt:-Cinitial-cache"><b><code>-C <initial-cache></code></b></a></li> <li><a href="#opt:-Dvar:typevalue"><b><code>-D <var>:<type>=<value></code></b></a></li> <li><a href="#opt:-Uglobbing_expr"><b><code>-U <globbing_expr></code></b></a></li> <li><a href="#opt:-Ggenerator-name"><b><code>-G <generator-name></code></b></a></li> <li><a href="#opt:-Wno-dev"><b><code>-Wno-dev</code></b></a></li> <li><a href="#opt:-Wdev"><b><code>-Wdev</code></b></a></li> <li><a href="#opt:-E"><b><code>-E</code></b></a></li> <li><a href="#opt:-i"><b><code>-i</code></b></a></li> <li><a href="#opt:-LAH"><b><code>-L[A][H]</code></b></a></li> <li><a href="#opt:-N"><b><code>-N</code></b></a></li> <li><a href="#opt:-Pfile"><b><code>-P <file></code></b></a></li> <li><a href="#opt:--graphvizfile"><b><code>--graphviz=[file]</code></b></a></li> <li><a href="#opt:--system-informationfile"><b><code>--system-information [file]</code></b></a></li> <li><a href="#opt:--debug-trycompile"><b><code>--debug-trycompile</code></b></a></li> <li><a href="#opt:--debug-output"><b><code>--debug-output</code></b></a></li> <li><a href="#opt:--help-commandcmdfile"><b><code>--help-command cmd [file]</code></b></a></li> <li><a href="#opt:--help-command-listfile"><b><code>--help-command-list [file]</code></b></a></li> <li><a href="#opt:--help-commandsfile"><b><code>--help-commands [file]</code></b></a></li> <li><a href="#opt:--help-compatcommandsfile"><b><code>--help-compatcommands [file]</code></b></a></li> <li><a href="#opt:--help-modulemodulefile"><b><code>--help-module module [file]</code></b></a></li> <li><a href="#opt:--help-module-listfile"><b><code>--help-module-list [file]</code></b></a></li> <li><a href="#opt:--help-modulesfile"><b><code>--help-modules [file]</code></b></a></li> <li><a href="#opt:--help-custom-modulesfile"><b><code>--help-custom-modules [file]</code></b></a></li> <li><a href="#opt:--help-propertypropfile"><b><code>--help-property prop [file]</code></b></a></li> <li><a href="#opt:--help-property-listfile"><b><code>--help-property-list [file]</code></b></a></li> <li><a href="#opt:--help-propertiesfile"><b><code>--help-properties [file]</code></b></a></li> <li><a href="#opt:--help-variablevarfile"><b><code>--help-variable var [file]</code></b></a></li> <li><a href="#opt:--help-variable-listfile"><b><code>--help-variable-list [file]</code></b></a></li> <li><a href="#opt:--help-variablesfile"><b><code>--help-variables [file]</code></b></a></li> <li><a href="#opt:--copyrightfile"><b><code>--copyright [file]</code></b></a></li> <li><a href="#opt:--help"><b><code>--help</code></b></a></li> <li><a href="#opt:--help-fullfile"><b><code>--help-full [file]</code></b></a></li> <li><a href="#opt:--help-htmlfile"><b><code>--help-html [file]</code></b></a></li> <li><a href="#opt:--help-manfile"><b><code>--help-man [file]</code></b></a></li> <li><a href="#opt:--versionfile"><b><code>--version [file]</code></b></a></li></ul>
<ul>
<li>
--- 43,47 ----
<h2><a name="section_Options"/>Options</h2>
<ul>
! <li><a href="#opt:-Cinitial-cache"><b><code>-C <initial-cache></code></b></a></li> <li><a href="#opt:-Dvar:typevalue"><b><code>-D <var>:<type>=<value></code></b></a></li> <li><a href="#opt:-Uglobbing_expr"><b><code>-U <globbing_expr></code></b></a></li> <li><a href="#opt:-Ggenerator-name"><b><code>-G <generator-name></code></b></a></li> <li><a href="#opt:-Wno-dev"><b><code>-Wno-dev</code></b></a></li> <li><a href="#opt:-Wdev"><b><code>-Wdev</code></b></a></li> <li><a href="#opt:-E"><b><code>-E</code></b></a></li> <li><a href="#opt:-i"><b><code>-i</code></b></a></li> <li><a href="#opt:-LAH"><b><code>-L[A][H]</code></b></a></li> <li><a href="#opt:-N"><b><code>-N</code></b></a></li> <li><a href="#opt:-Pfile"><b><code>-P <file></code></b></a></li> <li><a href="#opt:--graphvizfile"><b><code>--graphviz=[file]</code></b></a></li> <li><a href="#opt:--system-informationfile"><b><code>--system-information [file]</code></b></a></li> <li><a href="#opt:--debug-trycompile"><b><code>--debug-trycompile</code></b></a></li> <li><a href="#opt:--debug-output"><b><code>--debug-output</code></b></a></li> <li><a href="#opt:--help-commandcmdfile"><b><code>--help-command cmd [file]</code></b></a></li> <li><a href="#opt:--help-command-listfile"><b><code>--help-command-list [file]</code></b></a></li> <li><a href="#opt:--help-commandsfile"><b><code>--help-commands [file]</code></b></a></li> <li><a href="#opt:--help-compatcommandsfile"><b><code>--help-compatcommands [file]</code></b></a></li> <li><a href="#opt:--help-modulemodulefile"><b><code>--help-module module [file]</code></b></a></li> <li><a href="#opt:--help-module-listfile"><b><code>--help-module-list [file]</code></b></a></li> <li><a href="#opt:--help-modulesfile"><b><code>--help-modules [file]</code></b></a></li> <li><a href="#opt:--help-custom-modulesfile"><b><code>--help-custom-modules [file]</code></b></a></li> <li><a href="#opt:--help-policycmpfile"><b><code>--help-policy cmp [file]</code></b></a></li> <li><a href="#opt:--help-policiesfile"><b><code>--help-policies [file]</code></b></a></li> <li><a href="#opt:--help-propertypropfile"><b><code>--help-property prop [file]</code></b></a></li> <li><a href="#opt:--help-property-listfile"><b><code>--help-property-list [file]</code></b></a></li> <li><a href="#opt:--help-propertiesfile"><b><code>--help-properties [file]</code></b></a></li> <li><a href="#opt:--help-variablevarfile"><b><code>--help-variable var [file]</code></b></a></li> <li><a href="#opt:--help-variable-listfile"><b><code>--help-variable-list [file]</code></b></a></li> <li><a href="#opt:--help-variablesfile"><b><code>--help-variables [file]</code></b></a></li> <li><a href="#opt:--copyrightfile"><b><code>--copyright [file]</code></b></a></li> <li><a href="#opt:--help"><b><code>--help</code></b></a></li> <li><a href="#opt:--help-fullfile"><b><code>--help-full [file]</code></b></a></li> <li><a href="#opt:--help-htmlfile"><b><code>--help-html [file]</code></b></a></li> <li><a href="#opt:--help-manfile"><b><code>--help-man [file]</code></b></a></li> <li><a href="#opt:--versionfile"><b><code>--version [file]</code></b></a></li></ul>
<ul>
<li>
***************
*** 138,141 ****
--- 138,149 ----
</li>
<li>
+ <a name="opt:--help-policycmpfile"><b><code>--help-policy cmp [file]</code></b></a>: Print help for a single policy and exit.<br>
+ <p>Full documentation specific to the given policy is displayed.If a file is specified, the documentation is written into and the output format is determined depending on the filename suffix. Supported are man page, HTML, DocBook and plain text.
+ </li>
+ <li>
+ <a name="opt:--help-policiesfile"><b><code>--help-policies [file]</code></b></a>: Print help for all policies and exit.<br>
+ <p>Full documentation for all policies is displayed.If a file is specified, the documentation is written into and the output format is determined depending on the filename suffix. Supported are man page, HTML, DocBook and plain text.
+ </li>
+ <li>
<a name="opt:--help-propertypropfile"><b><code>--help-property prop [file]</code></b></a>: Print help for a single property and exit.<br>
<p>Full documentation specific to the given property is displayed.If a file is specified, the documentation is written into and the output format is determined depending on the filename suffix. Supported are man page, HTML, DocBook and plain text.
***************
*** 414,444 ****
<a name="command:find_file"><b><code>find_file</code></b></a>: Find the full path to a file.<br>
<pre> find_path(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_path(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_path(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a full path to named file. A cache entry named by <VAR> is created to store the result of this command. If the full path to a file is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_path is invoked with the same variable. The name of the full path to a file that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> INCLUDE<br></pre>
! <p>4. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_INCLUDE_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>5. Search the paths specified after PATHS or in the short-hand version of the command.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_path(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_path(<VAR> NAMES name)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.
</li>
<li>
<a name="command:find_library"><b><code>find_library</code></b></a>: Find a library.<br>
<pre> find_library(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_library(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_library(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a library. A cache entry named by <VAR> is created to store the result of this command. If the library is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_library is invoked with the same variable. The name of the library that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_LIBRARY_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_LIBRARY_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> LIB<br></pre>
! <p>4. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_LIBRARY_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>5. Search the paths specified after PATHS or in the short-hand version of the command.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_LIBRARY. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_library(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_library(<VAR> NAMES name)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.<br><p>If the library found is a framework, then VAR will be set to the full path to the framework <fullPath>/A.framework. When a full path to a framework is used as a library, CMake will use a -framework A, and a -F<fullPath> to link the framework to the target.
</li>
<li>
<a name="command:find_package"><b><code>find_package</code></b></a>: Load settings for an external project.<br>
<pre> find_package(<package> [major[.minor[.patch]]] [EXACT] [QUIET]<br> [[REQUIRED|COMPONENTS] [components...]])<br></pre>
! <p>Finds and loads settings from an external project. <package>_FOUND will be set to indicate whether the package was found. When the package is found package-specific information is provided through variables documented by the package itself. The QUIET option disables messages if the package cannot be found. The REQUIRED option stops processing with an error message if the package cannot be found. A package-specific list of components may be listed after the REQUIRED option or after the COMPONENTS option if no REQUIRED option is given. The "[major[.minor[.patch]]]" version argument specifies a desired version with which the package found should be compatible. The EXACT option requests that the version be matched exactly. Version support is currently provided only on a package-by-package basis (details below).<br><p>User code should generally look for packages using the above simple signature. The remainder of this command documentation specifies the full command signature and details of the search process. Project maintainers wishing to provide a package to be found by this command are encouraged to read on.<br><p>The command has two modes by which it searches for packages: "Module" mode and "Config" mode. Module mode is available when the command is invoked with the above reduced signature. CMake searches for a file called "Find<package>.cmake" in the CMAKE_MODULE_PATH followed by the CMake installation. If the file is found, it is read and processed by CMake. It is responsible for finding the package, checking the version, and producing any needed messages. Many find-modules provide limited or no support for versioning; check the module documentation. If no module is found the command proceeds to Config mode.<br><p>The complete Config mode command signature is:<br><pre> find_package(<package> [major[.minor[.patch]]] [EXACT] [QUIET]<br> [[REQUIRED|COMPONENTS] [components...]] [NO_MODULE]<br> [NAMES name1 [name2 ...]]<br> [CONFIGS config1 [config2 ...]]<br> [PATHS path1 [path2 ... ]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_BUILDS_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH])<br></pre>
<p>The NO_MODULE option may be used to skip Module mode explicitly. It is also implied by use of options not specified in the reduced signature. <br><p>Config mode attempts to locate a configuration file provided by the package to be found. A cache entry called <package>_DIR is created to hold the directory containing the file. By default the command searches for a package with the name <package>. If the NAMES option is given the names following it are used instead of <package>. The command searches for a file called "<name>Config.cmake" or "<lower-case-name>-config.cmake" for each name specified. A replacement set of possible configuration file names may be given using the CONFIGS option. The search procedure is specified below. Once found, the configuration file is read and processed by CMake. Since the file is provided by the package it already knows the location of package contents. The full path to the configuration file is stored in the cmake variable <package>_CONFIG.<br><p>If the package configuration file cannot be found CMake will generate an error describing the problem unless the QUIET argument is specified. If REQUIRED is specified and the package is not found a fatal error is generated and the configure step stops executing. If <package>_DIR has been set to a directory not containing a configuration file a fatal error is always generated because user intervention is required.<br><p>When the "[major[.minor[.patch]]]" version argument is specified Config mode will only find a version of the package that claims compatibility with the requested version. If the EXACT option is given only a version of the package claiming an exact match of the requested version may be found. CMake does not establish any convention for the meaning of version numbers. Package version numbers are checked by "version" files provided by the packages themselves. For a candidate package confguration file "<config-file>.cmake" the corresponding version file is located next to it and named either "<config-file>-version.cmake" or "<config-file>Version.cmake". If no such version file is available then the configuration file is assumed to not be compatible with any requested version. When a version file is found it is loaded to check the requested version number. The version file is loaded in a nested scope in which the following variables have been defined:<br><pre> PACKAGE_FIND_NAME = the <package> name<br> PACKAGE_FIND_VERSION = full requested version string<br> PACKAGE_FIND_VERSION_MAJOR = requested major version, if any<br> PACKAGE_FIND_VERSION_MINOR = requested minor version, if any<br> PACKAGE_FIND_VERSION_PATCH = requested patch version, if any<br></pre>
<p>The version file checks whether it satisfies the requested version and sets these variables:<br><pre> PACKAGE_VERSION = package version (major[.minor[.patch]])<br> PACKAGE_VERSION_EXACT = true if version is exact match<br> PACKAGE_VERSION_COMPATIBLE = true if version is compatible<br></pre>
--- 422,452 ----
<a name="command:find_file"><b><code>find_file</code></b></a>: Find the full path to a file.<br>
<pre> find_path(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_path(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_path(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [HINTS path1 [path2 ... ENV var]]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a full path to named file. A cache entry named by <VAR> is created to store the result of this command. If the full path to a file is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_path is invoked with the same variable. The name of the full path to a file that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the HINTS or PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> INCLUDE<br></pre>
! <p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_INCLUDE_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>6. Search the paths specified by the PATHS option or in the short-hand version of the command. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_path(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_path(<VAR> NAMES name)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.
</li>
<li>
<a name="command:find_library"><b><code>find_library</code></b></a>: Find a library.<br>
<pre> find_library(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_library(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_library(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [HINTS path1 [path2 ... ENV var]]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a library. A cache entry named by <VAR> is created to store the result of this command. If the library is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_library is invoked with the same variable. The name of the library that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the HINTS or PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_LIBRARY_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_LIBRARY_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> LIB<br></pre>
! <p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_LIBRARY_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>6. Search the paths specified by the PATHS option or in the short-hand version of the command. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_LIBRARY. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_library(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_library(<VAR> NAMES name)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.<br><p>If the library found is a framework, then VAR will be set to the full path to the framework <fullPath>/A.framework. When a full path to a framework is used as a library, CMake will use a -framework A, and a -F<fullPath> to link the framework to the target.
</li>
<li>
<a name="command:find_package"><b><code>find_package</code></b></a>: Load settings for an external project.<br>
<pre> find_package(<package> [major[.minor[.patch]]] [EXACT] [QUIET]<br> [[REQUIRED|COMPONENTS] [components...]])<br></pre>
! <p>Finds and loads settings from an external project. <package>_FOUND will be set to indicate whether the package was found. When the package is found package-specific information is provided through variables documented by the package itself. The QUIET option disables messages if the package cannot be found. The REQUIRED option stops processing with an error message if the package cannot be found. A package-specific list of components may be listed after the REQUIRED option or after the COMPONENTS option if no REQUIRED option is given. The "[major[.minor[.patch]]]" version argument specifies a desired version with which the package found should be compatible. The EXACT option requests that the version be matched exactly. Version support is currently provided only on a package-by-package basis (details below).<br><p>User code should generally look for packages using the above simple signature. The remainder of this command documentation specifies the full command signature and details of the search process. Project maintainers wishing to provide a package to be found by this command are encouraged to read on.<br><p>The command has two modes by which it searches for packages: "Module" mode and "Config" mode. Module mode is available when the command is invoked with the above reduced signature. CMake searches for a file called "Find<package>.cmake" in the CMAKE_MODULE_PATH followed by the CMake installation. If the file is found, it is read and processed by CMake. It is responsible for finding the package, checking the version, and producing any needed messages. Many find-modules provide limited or no support for versioning; check the module documentation. If no module is found the command proceeds to Config mode.<br><p>The complete Config mode command signature is:<br><pre> find_package(<package> [major[.minor[.patch]]] [EXACT] [QUIET]<br> [[REQUIRED|COMPONENTS] [components...]] [NO_MODULE]<br> [NAMES name1 [name2 ...]]<br> [CONFIGS config1 [config2 ...]]<br> [HINTS path1 [path2 ... ]]<br> [PATHS path1 [path2 ... ]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_BUILDS_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH])<br></pre>
<p>The NO_MODULE option may be used to skip Module mode explicitly. It is also implied by use of options not specified in the reduced signature. <br><p>Config mode attempts to locate a configuration file provided by the package to be found. A cache entry called <package>_DIR is created to hold the directory containing the file. By default the command searches for a package with the name <package>. If the NAMES option is given the names following it are used instead of <package>. The command searches for a file called "<name>Config.cmake" or "<lower-case-name>-config.cmake" for each name specified. A replacement set of possible configuration file names may be given using the CONFIGS option. The search procedure is specified below. Once found, the configuration file is read and processed by CMake. Since the file is provided by the package it already knows the location of package contents. The full path to the configuration file is stored in the cmake variable <package>_CONFIG.<br><p>If the package configuration file cannot be found CMake will generate an error describing the problem unless the QUIET argument is specified. If REQUIRED is specified and the package is not found a fatal error is generated and the configure step stops executing. If <package>_DIR has been set to a directory not containing a configuration file a fatal error is always generated because user intervention is required.<br><p>When the "[major[.minor[.patch]]]" version argument is specified Config mode will only find a version of the package that claims compatibility with the requested version. If the EXACT option is given only a version of the package claiming an exact match of the requested version may be found. CMake does not establish any convention for the meaning of version numbers. Package version numbers are checked by "version" files provided by the packages themselves. For a candidate package confguration file "<config-file>.cmake" the corresponding version file is located next to it and named either "<config-file>-version.cmake" or "<config-file>Version.cmake". If no such version file is available then the configuration file is assumed to not be compatible with any requested version. When a version file is found it is loaded to check the requested version number. The version file is loaded in a nested scope in which the following variables have been defined:<br><pre> PACKAGE_FIND_NAME = the <package> name<br> PACKAGE_FIND_VERSION = full requested version string<br> PACKAGE_FIND_VERSION_MAJOR = requested major version, if any<br> PACKAGE_FIND_VERSION_MINOR = requested minor version, if any<br> PACKAGE_FIND_VERSION_PATCH = requested patch version, if any<br></pre>
<p>The version file checks whether it satisfies the requested version and sets these variables:<br><pre> PACKAGE_VERSION = package version (major[.minor[.patch]])<br> PACKAGE_VERSION_EXACT = true if version is exact match<br> PACKAGE_VERSION_COMPATIBLE = true if version is compatible<br></pre>
***************
*** 447,484 ****
<p>in order to find a package. Package maintainers providing CMake package configuration files are encouraged to name and install them such that the procedure outlined below will find them without requiring use of additional options.<br><p>CMake constructs a set of possible installation prefixes for the package. Under each prefix several directories are searched for a configuration file. The tables below show the directories searched. Each entry is meant for installation trees following Windows (W), UNIX (U), or Apple (A) conventions.<br><pre> <prefix>/ (W)<br> <prefix>/(cmake|CMake)/ (W)<br> <prefix>/(share|lib)/<name>*/ (U)<br> <prefix>/(share|lib)/<name>*/(cmake|CMake)/ (U)<br></pre>
<p>On systems supporting OS X Frameworks and Application Bundles the following directories are searched for frameworks or bundles containing a configuration file:<br><pre> <prefix>/<name>.framework/Resources/ (A)<br> <prefix>/<name>.framework/Resources/CMake/ (A)<br> <prefix>/<name>.framework/Versions/*/Resources/ (A)<br> <prefix>/<name>.framework/Versions/*/Resources/CMake/ (A)<br> <prefix>/<name>.app/Contents/Resources/ (A)<br> <prefix>/<name>.app/Contents/Resources/CMake/ (A)<br></pre>
! <p>In all cases the <name> is treated as case-insensitive and corresponds to any of the names specified (<package> or names given by NAMES). If PATH_SUFFIXES is specified the suffixes are appended to each (W) or (U) directory entry one-by-one.<br><p>This set of directories is intended to work in cooperation with projects that provide configuration files in their installation trees. Directories above marked with (W) are intended for installations on Windows where the prefix may point at the top of an application's installation directory. Those marked with (U) are intended for installations on UNIX platforms where the prefix is shared by multiple packages. This is merely a convention, so all (W) and (U) directories are still searched on all platforms. Directories marked with (A) are intended for installations on Apple platforms. The cmake variables CMAKE_FIND_FRAMEWORK and CMAKE_FIND_APPBUNDLE determine the order of preference as specified below.<br><p>The set of installation prefixes is constructed using the following steps. If NO_DEFAULT_PATH is specified steps 1-5 are skipped.<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> CMAKE_PREFIX_PATH<br> CMAKE_FRAMEWORK_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> CMAKE_PREFIX_PATH<br> CMAKE_FRAMEWORK_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is passed. Path entries ending in "/bin" or "/sbin" are automatically converted to their parent directories.<br><pre> PATH<br></pre>
! <p>4. Search project build trees recently configured in a CMake GUI. This can be skipped if NO_CMAKE_BUILDS_PATH is passed. It is intended for the case when a user is building multiple dependent projects one after another.<br><p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br> CMAKE_SYSTEM_APPBUNDLE_PATH<br></pre>
! <p>6. Search paths specified by the PATHS option.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_PACKAGE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_package(<package> PATHS paths... NO_DEFAULT_PATH)<br> find_package(<package>)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.
</li>
<li>
<a name="command:find_path"><b><code>find_path</code></b></a>: Find the directory containing a file.<br>
<pre> find_path(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_path(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_path(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a directory containing the named file. A cache entry named by <VAR> is created to store the result of this command. If the file in a directory is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_path is invoked with the same variable. The name of the file in a directory that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> INCLUDE<br></pre>
! <p>4. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_INCLUDE_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>5. Search the paths specified after PATHS or in the short-hand version of the command.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_path(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_path(<VAR> NAMES name)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.<br><p>When searching for frameworks, if the file is specified as A/b.h, then the framework search will look for A.framework/Headers/b.h. If that is found the path will be set to the path to the framework. CMake will convert this to the correct -F option to include the file.
</li>
<li>
<a name="command:find_program"><b><code>find_program</code></b></a>: Find an executable program.<br>
<pre> find_program(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_program(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_program(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a program. A cache entry named by <VAR> is created to store the result of this command. If the program is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_program is invoked with the same variable. The name of the program that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_PROGRAM_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_PROGRAM_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> <br></pre>
! <p>4. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_PROGRAM_PATH<br> CMAKE_SYSTEM_APPBUNDLE_PATH<br></pre>
! <p>5. Search the paths specified after PATHS or in the short-hand version of the command.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_PROGRAM. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_program(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_program(<VAR> NAMES name)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.
</li>
<li>
--- 455,492 ----
<p>in order to find a package. Package maintainers providing CMake package configuration files are encouraged to name and install them such that the procedure outlined below will find them without requiring use of additional options.<br><p>CMake constructs a set of possible installation prefixes for the package. Under each prefix several directories are searched for a configuration file. The tables below show the directories searched. Each entry is meant for installation trees following Windows (W), UNIX (U), or Apple (A) conventions.<br><pre> <prefix>/ (W)<br> <prefix>/(cmake|CMake)/ (W)<br> <prefix>/(share|lib)/<name>*/ (U)<br> <prefix>/(share|lib)/<name>*/(cmake|CMake)/ (U)<br></pre>
<p>On systems supporting OS X Frameworks and Application Bundles the following directories are searched for frameworks or bundles containing a configuration file:<br><pre> <prefix>/<name>.framework/Resources/ (A)<br> <prefix>/<name>.framework/Resources/CMake/ (A)<br> <prefix>/<name>.framework/Versions/*/Resources/ (A)<br> <prefix>/<name>.framework/Versions/*/Resources/CMake/ (A)<br> <prefix>/<name>.app/Contents/Resources/ (A)<br> <prefix>/<name>.app/Contents/Resources/CMake/ (A)<br></pre>
! <p>In all cases the <name> is treated as case-insensitive and corresponds to any of the names specified (<package> or names given by NAMES). If PATH_SUFFIXES is specified the suffixes are appended to each (W) or (U) directory entry one-by-one.<br><p>This set of directories is intended to work in cooperation with projects that provide configuration files in their installation trees. Directories above marked with (W) are intended for installations on Windows where the prefix may point at the top of an application's installation directory. Those marked with (U) are intended for installations on UNIX platforms where the prefix is shared by multiple packages. This is merely a convention, so all (W) and (U) directories are still searched on all platforms. Directories marked with (A) are intended for installations on Apple platforms. The cmake variables CMAKE_FIND_FRAMEWORK and CMAKE_FIND_APPBUNDLE determine the order of preference as specified below.<br><p>The set of installation prefixes is constructed using the following steps. If NO_DEFAULT_PATH is specified all NO_* options are enabled.<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> CMAKE_PREFIX_PATH<br> CMAKE_FRAMEWORK_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> CMAKE_PREFIX_PATH<br> CMAKE_FRAMEWORK_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>3. Search paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is passed. Path entries ending in "/bin" or "/sbin" are automatically converted to their parent directories.<br><pre> PATH<br></pre>
! <p>5. Search project build trees recently configured in a CMake GUI. This can be skipped if NO_CMAKE_BUILDS_PATH is passed. It is intended for the case when a user is building multiple dependent projects one after another.<br><p>6. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br> CMAKE_SYSTEM_APPBUNDLE_PATH<br></pre>
! <p>7. Search paths specified by the PATHS option. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_PACKAGE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_package(<package> PATHS paths... NO_DEFAULT_PATH)<br> find_package(<package>)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.
</li>
<li>
<a name="command:find_path"><b><code>find_path</code></b></a>: Find the directory containing a file.<br>
<pre> find_path(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_path(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_path(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [HINTS path1 [path2 ... ENV var]]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a directory containing the named file. A cache entry named by <VAR> is created to store the result of this command. If the file in a directory is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_path is invoked with the same variable. The name of the file in a directory that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the HINTS or PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> INCLUDE<br></pre>
! <p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_INCLUDE_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>6. Search the paths specified by the PATHS option or in the short-hand version of the command. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_path(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_path(<VAR> NAMES name)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.<br><p>When searching for frameworks, if the file is specified as A/b.h, then the framework search will look for A.framework/Headers/b.h. If that is found the path will be set to the path to the framework. CMake will convert this to the correct -F option to include the file.
</li>
<li>
<a name="command:find_program"><b><code>find_program</code></b></a>: Find an executable program.<br>
<pre> find_program(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_program(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_program(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [HINTS path1 [path2 ... ENV var]]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a program. A cache entry named by <VAR> is created to store the result of this command. If the program is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_program is invoked with the same variable. The name of the program that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the HINTS or PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_PROGRAM_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_PROGRAM_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>3. Search the paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> <br></pre>
! <p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_PROGRAM_PATH<br> CMAKE_SYSTEM_APPBUNDLE_PATH<br></pre>
! <p>6. Search the paths specified by the PATHS option or in the short-hand version of the command. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_PROGRAM. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_program(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_program(<VAR> NAMES name)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.
</li>
<li>
***************
*** 500,504 ****
<a name="command:get_cmake_property"><b><code>get_cmake_property</code></b></a>: Get a property of the CMake instance.<br>
<pre> get_cmake_property(VAR property)<br></pre>
! <p>Get a property from the CMake instance. The value of the property is stored in the variable VAR. If the property is not found, CMake will report an error. Some supported properties include: VARIABLES, CACHE_VARIABLES, COMMANDS, and MACROS.
</li>
<li>
--- 508,512 ----
<a name="command:get_cmake_property"><b><code>get_cmake_property</code></b></a>: Get a property of the CMake instance.<br>
<pre> get_cmake_property(VAR property)<br></pre>
! <p>Get a property from the CMake instance. The value of the property is stored in the variable VAR. If the property is not found, CMake will report an error. Some supported properties include: VARIABLES, CACHE_VARIABLES, COMMANDS, MACROS, and COMPONENTS.
</li>
<li>
***************
*** 760,764 ****
<h2><a name="section_Properties of Global Scope"/>Properties of Global Scope</h2>
<ul>
! <li><a href="#prop_global:ALLOW_DUPLICATE_CUSTOM_TARGETS"><b><code>ALLOW_DUPLICATE_CUSTOM_TARGETS</code></b></a></li> <li><a href="#prop_global:DISABLED_FEATURES"><b><code>DISABLED_FEATURES</code></b></a></li> <li><a href="#prop_global:ENABLED_FEATURES"><b><code>ENABLED_FEATURES</code></b></a></li> <li><a href="#prop_global:FIND_LIBRARY_USE_LIB64_PATHS"><b><code>FIND_LIBRARY_USE_LIB64_PATHS</code></b></a></li> <li><a href="#prop_global:GLOBAL_DEPENDS_DEBUG_MODE"><b><code>GLOBAL_DEPENDS_DEBUG_MODE</code></b></a></li> <li><a href="#prop_global:IN_TRY_COMPILE"><b><code>IN_TRY_COMPILE</code></b></a></li> <li><a href="#prop_global:PACKAGES_FOUND"><b><code>PACKAGES_FOUND</code></b></a></li> <li><a href="#prop_global:PACKAGES_NOT_FOUND"><b><code>PACKAGES_NOT_FOUND</code></b></a></li> <li><a href="#prop_global:REPORT_UNDEFINED_PROPERTIES"><b><code>REPORT_UNDEFINED_PROPERTIES</code></b></a></li> <li><a href="#prop_global:TARGET_ARCHIVES_MAY_BE_SHARED_LIBS"><b><code>TARGET_ARCHIVES_MAY_BE_SHARED_LIBS</code></b></a></li> <li><a href="#prop_global:TARGET_SUPPORTS_SHARED_LIBS"><b><code>TARGET_SUPPORTS_SHARED_LIBS</code></b></a></li> <li><a href="#prop_global:__CMAKE_DELETE_CACHE_CHANGE_VARS_"><b><code>__CMAKE_DELETE_CACHE_CHANGE_VARS_</code></b></a></li></ul>
<ul>
<li>
--- 768,772 ----
<h2><a name="section_Properties of Global Scope"/>Properties of Global Scope</h2>
<ul>
! <li><a href="#prop_global:ALLOW_DUPLICATE_CUSTOM_TARGETS"><b><code>ALLOW_DUPLICATE_CUSTOM_TARGETS</code></b></a></li> <li><a href="#prop_global:DISABLED_FEATURES"><b><code>DISABLED_FEATURES</code></b></a></li> <li><a href="#prop_global:ENABLED_FEATURES"><b><code>ENABLED_FEATURES</code></b></a></li> <li><a href="#prop_global:ENABLED_LANGUAGES"><b><code>ENABLED_LANGUAGES</code></b></a></li> <li><a href="#prop_global:FIND_LIBRARY_USE_LIB64_PATHS"><b><code>FIND_LIBRARY_USE_LIB64_PATHS</code></b></a></li> <li><a href="#prop_global:GLOBAL_DEPENDS_DEBUG_MODE"><b><code>GLOBAL_DEPENDS_DEBUG_MODE</code></b></a></li> <li><a href="#prop_global:IN_TRY_COMPILE"><b><code>IN_TRY_COMPILE</code></b></a></li> <li><a href="#prop_global:PACKAGES_FOUND"><b><code>PACKAGES_FOUND</code></b></a></li> <li><a href="#prop_global:PACKAGES_NOT_FOUND"><b><code>PACKAGES_NOT_FOUND</code></b></a></li> <li><a href="#prop_global:REPORT_UNDEFINED_PROPERTIES"><b><code>REPORT_UNDEFINED_PROPERTIES</code></b></a></li> <li><a href="#prop_global:TARGET_ARCHIVES_MAY_BE_SHARED_LIBS"><b><code>TARGET_ARCHIVES_MAY_BE_SHARED_LIBS</code></b></a></li> <li><a href="#prop_global:TARGET_SUPPORTS_SHARED_LIBS"><b><code>TARGET_SUPPORTS_SHARED_LIBS</code></b></a></li> <li><a href="#prop_global:__CMAKE_DELETE_CACHE_CHANGE_VARS_"><b><code>__CMAKE_DELETE_CACHE_CHANGE_VARS_</code></b></a></li></ul>
<ul>
<li>
***************
*** 775,778 ****
--- 783,790 ----
</li>
<li>
+ <a name="prop_global:ENABLED_LANGUAGES"><b><code>ENABLED_LANGUAGES</code></b></a>: Read-only property that contains the list of currently enabled languages<br>
+ <p>Set to list of currently enabled lanauges.
+ </li>
+ <li>
<a name="prop_global:FIND_LIBRARY_USE_LIB64_PATHS"><b><code>FIND_LIBRARY_USE_LIB64_PATHS</code></b></a>: Whether FIND_LIBRARY should automatically search lib64 directories.<br>
<p>FIND_LIBRARY_USE_LIB64_PATHS is a boolean specifying whether the FIND_LIBRARY command should automatically search the lib64 variant of directories called lib in the search path when building 64-bit binaries.
***************
*** 813,817 ****
<h2><a name="section_Properties on Directories"/>Properties on Directories</h2>
<ul>
! <li><a href="#prop_dir:ADDITIONAL_MAKE_CLEAN_FILES"><b><code>ADDITIONAL_MAKE_CLEAN_FILES</code></b></a></li> <li><a href="#prop_dir:CLEAN_NO_CUSTOM"><b><code>CLEAN_NO_CUSTOM</code></b></a></li> <li><a href="#prop_dir:COMPILE_DEFINITIONS"><b><code>COMPILE_DEFINITIONS</code></b></a></li> <li><a href="#prop_dir:COMPILE_DEFINITIONS_CONFIG"><b><code>COMPILE_DEFINITIONS_<CONFIG></code></b></a></li> <li><a href="#prop_dir:EXCLUDE_FROM_ALL"><b><code>EXCLUDE_FROM_ALL</code></b></a></li> <li><a href="#prop_dir:LISTFILE_STACK"><b><code>LISTFILE_STACK</code></b></a></li> <li><a href="#prop_dir:TEST_INCLUDE_FILE"><b><code>TEST_INCLUDE_FILE</code></b></a></li></ul>
<ul>
<li>
--- 825,829 ----
<h2><a name="section_Properties on Directories"/>Properties on Directories</h2>
<ul>
! <li><a href="#prop_dir:ADDITIONAL_MAKE_CLEAN_FILES"><b><code>ADDITIONAL_MAKE_CLEAN_FILES</code></b></a></li> <li><a href="#prop_dir:CACHE_VARIABLES"><b><code>CACHE_VARIABLES</code></b></a></li> <li><a href="#prop_dir:CLEAN_NO_CUSTOM"><b><code>CLEAN_NO_CUSTOM</code></b></a></li> <li><a href="#prop_dir:COMPILE_DEFINITIONS"><b><code>COMPILE_DEFINITIONS</code></b></a></li> <li><a href="#prop_dir:COMPILE_DEFINITIONS_CONFIG"><b><code>COMPILE_DEFINITIONS_<CONFIG></code></b></a></li> <li><a href="#prop_dir:DEFINITIONS"><b><code>DEFINITIONS</code></b></a></li> <li><a href="#prop_dir:EXCLUDE_FROM_ALL"><b><code>EXCLUDE_FROM_ALL</code></b></a></li> <li><a href="#prop_dir:IMPLICIT_DEPENDS_INCLUDE_TRANSFORM"><b><code>IMPLICIT_DEPENDS_INCLUDE_TRANSFORM</code></b></a></li> <li><a href="#prop_dir:INCLUDE_DIRECTORIES"><b><code>INCLUDE_DIRECTORIES</code></b></a></li> <li><a href="#prop_dir:INCLUDE_REGULAR_EXPRESSION"><b><code>INCLUDE_REGULAR_EXPRESSION</code></b></a></li> <li><a href="#prop_dir:LINK_DIRECTORIES"><b><code>LINK_DIRECTORIES</code></b></a></li> <li><a href="#prop_dir:LISTFILE_STACK"><b><code>LISTFILE_STACK</code></b></a></li> <li><a href="#prop_dir:MACROS"><b><code>MACROS</code></b></a></li> <li><a href="#prop_dir:PARENT_DIRECTORY"><b><code>PARENT_DIRECTORY</code></b></a></li> <li><a href="#prop_dir:TEST_INCLUDE_FILE"><b><code>TEST_INCLUDE_FILE</code></b></a></li> <li><a href="#prop_dir:VARIABLES"><b><code>VARIABLES</code></b></a></li></ul>
<ul>
<li>
***************
*** 820,823 ****
--- 832,839 ----
</li>
<li>
+ <a name="prop_dir:CACHE_VARIABLES"><b><code>CACHE_VARIABLES</code></b></a>: List of cache variables available in the current directory.<br>
+ <p>This read-only property specifies the list of CMake cache variables currently defined. It is intended for debugging purposes.
+ </li>
+ <li>
<a name="prop_dir:CLEAN_NO_CUSTOM"><b><code>CLEAN_NO_CUSTOM</code></b></a>: Should the output of custom commands be left.<br>
<p>If this is true then the outputs of custom commands for this directory will not be removed during the "make clean" stage.
***************
*** 832,850 ****
</li>
<li>
<a name="prop_dir:EXCLUDE_FROM_ALL"><b><code>EXCLUDE_FROM_ALL</code></b></a>: Exclude the directory from the all target of its parent.<br>
<p>A property on a directory that indicates if its targets are excluded from the default build target. If it is not, then with a Makefile for example typing make will cause the targets to be built. The same concept applies to the default build of other generators.
</li>
<li>
<a name="prop_dir:LISTFILE_STACK"><b><code>LISTFILE_STACK</code></b></a>: The current stack of listfiles being processed.<br>
<p>This property is mainly useful when trying to debug errors in your CMake scripts. It returns a list of what list files are currently being processed, in order. So if one listfile does an INCLUDE command then that is effectively pushing the included listfile onto the stack.
</li>
<li>
<a name="prop_dir:TEST_INCLUDE_FILE"><b><code>TEST_INCLUDE_FILE</code></b></a>: A cmake file that will be included when ctest is run.<br>
<p>If you specify TEST_INCLUDE_FILE, that file will be included and processed when ctest is run on the directory.
</li>
</ul>
<h2><a name="section_Properties on Targets"/>Properties on Targets</h2>
<ul>
! <li><a href="#prop_tgt:ARCHIVE_OUTPUT_DIRECTORY"><b><code>ARCHIVE_OUTPUT_DIRECTORY</code></b></a></li> <li><a href="#prop_tgt:BUILD_WITH_INSTALL_RPATH"><b><code>BUILD_WITH_INSTALL_RPATH</code></b></a></li> <li><a href="#prop_tgt:CLEAN_DIRECT_OUTPUT"><b><code>CLEAN_DIRECT_OUTPUT</code></b></a></li> <li><a href="#prop_tgt:COMPILE_DEFINITIONS"><b><code>COMPILE_DEFINITIONS</code></b></a></li> <li><a href="#prop_tgt:COMPILE_DEFINITIONS_CONFIG"><b><code>COMPILE_DEFINITIONS_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:COMPILE_FLAGS"><b><code>COMPILE_FLAGS</code></b></a></li> <li><a href="#prop_tgt:DEBUG_POSTFIX"><b><code>DEBUG_POSTFIX</code></b></a></li> <li><a href="#prop_tgt:DEFINE_SYMBOL"><b><code>DEFINE_SYMBOL</code></b></a></li> <li><a href="#prop_tgt:ENABLE_EXPORTS"><b><code>ENABLE_EXPORTS</code></b></a></li> <li><a href="#prop_tgt:EXCLUDE_FROM_ALL"><b><code>EXCLUDE_FROM_ALL</code></b></a></li> <li><a href="#prop_tgt:EchoString"><b><code>EchoString</code></b></a></li> <li><a href="#prop_tgt:FRAMEWORK"><b><code>FRAMEWORK</code></b></a></li> <li><a href="#prop_tgt:Fortran_MODULE_DIRECTORY"><b><code>Fortran_MODULE_DIRECTORY</code></b></a></li> <li><a href="#prop_tgt:GENERATOR_FILE_NAME"><b><code>GENERATOR_FILE_NAME</code></b></a></li> <li><a href="#prop_tgt:HAS_CXX"><b><code>HAS_CXX</code></b></a></li> <li><a href="#prop_tgt:IMPORTED"><b><code>IMPORTED</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_CONFIGURATIONS"><b><code>IMPORTED_CONFIGURATIONS</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_IMPLIB"><b><code>IMPORTED_IMPLIB</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_IMPLIB_CONFIG"><b><code>IMPORTED_IMPLIB_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LINK_DEPENDENT_LIBRARIES"><b><code>IMPORTED_LINK_DEPENDENT_LIBRARIES</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LINK_DEPENDENT_LIBRARIES_CONFIG"><b><code>IMPORTED_LINK_DEPENDENT_LIBRARIES_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LINK_INTERFACE_LIBRARIES"><b><code>IMPORTED_LINK_INTERFACE_LIBRARIES</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LINK_INTERFACE_LIBRARIES_CONFIG"><b><code>IMPORTED_LINK_INTERFACE_LIBRARIES_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LOCATION"><b><code>IMPORTED_LOCATION</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LOCATION_CONFIG"><b><code>IMPORTED_LOCATION_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORTED_SONAME"><b><code>IMPORTED_SONAME</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_SONAME_CONFIG"><b><code>IMPORTED_SONAME_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORT_PREFIX"><b><code>IMPORT_PREFIX</code></b></a></li> <li><a href="#prop_tgt:IMPORT_SUFFIX"><b><code>IMPORT_SUFFIX</code></b></a></li> <li><a href="#prop_tgt:INSTALL_NAME_DIR"><b><code>INSTALL_NAME_DIR</code></b></a></li> <li><a href="#prop_tgt:INSTALL_RPATH"><b><code>INSTALL_RPATH</code></b></a></li> <li><a href="#prop_tgt:INSTALL_RPATH_USE_LINK_PATH"><b><code>INSTALL_RPATH_USE_LINK_PATH</code></b></a></li> <li><a href="#prop_tgt:LIBRARY_OUTPUT_DIRECTORY"><b><code>LIBRARY_OUTPUT_DIRECTORY</code></b></a></li> <li><a href="#prop_tgt:LINKER_LANGUAGE"><b><code>LINKER_LANGUAGE</code></b></a></li> <li><a href="#prop_tgt:LINK_FLAGS"><b><code>LINK_FLAGS</code></b></a></li> <li><a href="#prop_tgt:LINK_FLAGS_CONFIG"><b><code>LINK_FLAGS_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:LINK_INTERFACE_LIBRARIES"><b><code>LINK_INTERFACE_LIBRARIES</code></b></a></li> <li><a href="#prop_tgt:LINK_INTERFACE_LIBRARIES_CONFIG"><b><code>LINK_INTERFACE_LIBRARIES_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:LINK_SEARCH_END_STATIC"><b><code>LINK_SEARCH_END_STATIC</code></b></a></li> <li><a href="#prop_tgt:LOCATION"><b><code>LOCATION</code></b></a></li> <li><a href="#prop_tgt:LOCATION_CONFIG"><b><code>LOCATION_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:MACOSX_BUNDLE"><b><code>MACOSX_BUNDLE</code></b></a></li> <li><a href="#prop_tgt:MAP_IMPORTED_CONFIG_CONFIG"><b><code>MAP_IMPORTED_CONFIG_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:OUTPUT_NAME"><b><code>OUTPUT_NAME</code></b></a></li> <li><a href="#prop_tgt:POST_INSTALL_SCRIPT"><b><code>POST_INSTALL_SCRIPT</code></b></a></li> <li><a href="#prop_tgt:PREFIX"><b><code>PREFIX</code></b></a></li> <li><a href="#prop_tgt:PRE_INSTALL_SCRIPT"><b><code>PRE_INSTALL_SCRIPT</code></b></a></li> <li><a href="#prop_tgt:PRIVATE_HEADER"><b><code>PRIVATE_HEADER</code></b></a></li> <li><a href="#prop_tgt:PUBLIC_HEADER"><b><code>PUBLIC_HEADER</code></b></a></li> <li><a href="#prop_tgt:RESOURCE"><b><code>RESOURCE</code></b></a></li> <li><a href="#prop_tgt:RUNTIME_OUTPUT_DIRECTORY"><b><code>RUNTIME_OUTPUT_DIRECTORY</code></b></a></li> <li><a href="#prop_tgt:SKIP_BUILD_RPATH"><b><code>SKIP_BUILD_RPATH</code></b></a></li> <li><a href="#prop_tgt:SOURCES"><b><code>SOURCES</code></b></a></li> <li><a href="#prop_tgt:SOVERSION"><b><code>SOVERSION</code></b></a></li> <li><a href="#prop_tgt:STATIC_LIBRARY_FLAGS"><b><code>STATIC_LIBRARY_FLAGS</code></b></a></li> <li><a href="#prop_tgt:SUFFIX"><b><code>SUFFIX</code></b></a></li> <li><a href="#prop_tgt:VERSION"><b><code>VERSION</code></b></a></li> <li><a href="#prop_tgt:WIN32_EXECUTABLE"><b><code>WIN32_EXECUTABLE</code></b></a></li> <li><a href="#prop_tgt:XCODE_ATTRIBUTE_an-attribute"><b><code>XCODE_ATTRIBUTE_<an-attribute></code></b></a></li></ul>
<ul>
<li>
--- 848,901 ----
</li>
<li>
+ <a name="prop_dir:DEFINITIONS"><b><code>DEFINITIONS</code></b></a>: For CMake 2.4 compatibility only. Use COMPILE_DEFINITIONS instead.<br>
+ <p>This read-only property specifies the list of flags given so far to the add_definitions command. It is intended for debugging purposes. Use the COMPILE_DEFINITIONS instead.
+ </li>
+ <li>
<a name="prop_dir:EXCLUDE_FROM_ALL"><b><code>EXCLUDE_FROM_ALL</code></b></a>: Exclude the directory from the all target of its parent.<br>
<p>A property on a directory that indicates if its targets are excluded from the default build target. If it is not, then with a Makefile for example typing make will cause the targets to be built. The same concept applies to the default build of other generators.
</li>
<li>
+ <a name="prop_dir:IMPLICIT_DEPENDS_INCLUDE_TRANSFORM"><b><code>IMPLICIT_DEPENDS_INCLUDE_TRANSFORM</code></b></a>: Specify #include line transforms for dependencies in a directory.<br>
+ <p>This property specifies rules to transform macro-like #include lines during implicit dependency scanning of C and C++ source files. The list of rules must be semicolon-separated with each entry of the form "A_MACRO(%)=value-with-%" (the % must be literal). During dependency scanning occurrences of A_MACRO(...) on #include lines will be replaced by the value given with the macro argument substituted for '%'. For example, the entry<br><pre> MYDIR(%)=<mydir/%><br></pre>
+ <p>will convert lines of the form<br><pre> #include MYDIR(myheader.h)<br></pre>
+ <p>to<br><pre> #include <mydir/myheader.h><br></pre>
+ <p>allowing the dependency to be followed.<br><p>This property applies to sources in all targets within a directory. The property value is initialized in each directory by its value in the directory's parent.
+ </li>
+ <li>
+ <a name="prop_dir:INCLUDE_DIRECTORIES"><b><code>INCLUDE_DIRECTORIES</code></b></a>: List of preprocessor include file search directories.<br>
+ <p>This read-only property specifies the list of directories given so far to the include_directories command. It is intended for debugging purposes.
+ </li>
+ <li>
+ <a name="prop_dir:INCLUDE_REGULAR_EXPRESSION"><b><code>INCLUDE_REGULAR_EXPRESSION</code></b></a>: Include file scanning regular expression.<br>
+ <p>This read-only property specifies the regular expression used during dependency scanning to match include files that should be followed. See the include_regular_expression command.
+ </li>
+ <li>
+ <a name="prop_dir:LINK_DIRECTORIES"><b><code>LINK_DIRECTORIES</code></b></a>: List of linker search directories.<br>
+ <p>This read-only property specifies the list of directories given so far to the link_directories command. It is intended for debugging purposes.
+ </li>
+ <li>
<a name="prop_dir:LISTFILE_STACK"><b><code>LISTFILE_STACK</code></b></a>: The current stack of listfiles being processed.<br>
<p>This property is mainly useful when trying to debug errors in your CMake scripts. It returns a list of what list files are currently being processed, in order. So if one listfile does an INCLUDE command then that is effectively pushing the included listfile onto the stack.
</li>
<li>
+ <a name="prop_dir:MACROS"><b><code>MACROS</code></b></a>: List of macro commands available in the current directory.<br>
+ <p>This read-only property specifies the list of CMake macros currently defined. It is intended for debugging purposes. See the macro command.
+ </li>
+ <li>
+ <a name="prop_dir:PARENT_DIRECTORY"><b><code>PARENT_DIRECTORY</code></b></a>: Source directory that added current subdirectory.<br>
+ <p>This read-only property specifies the source directory that added the current source directory as a subdirectory of the build. In the top-level directory the value is the empty-string.
+ </li>
+ <li>
<a name="prop_dir:TEST_INCLUDE_FILE"><b><code>TEST_INCLUDE_FILE</code></b></a>: A cmake file that will be included when ctest is run.<br>
<p>If you specify TEST_INCLUDE_FILE, that file will be included and processed when ctest is run on the directory.
</li>
+ <li>
+ <a name="prop_dir:VARIABLES"><b><code>VARIABLES</code></b></a>: List of variables defined in the current directory.<br>
+ <p>This read-only property specifies the list of CMake variables currently defined. It is intended for debugging purposes.
+ </li>
</ul>
<h2><a name="section_Properties on Targets"/>Properties on Targets</h2>
<ul>
! <li><a href="#prop_tgt:ARCHIVE_OUTPUT_DIRECTORY"><b><code>ARCHIVE_OUTPUT_DIRECTORY</code></b></a></li> <li><a href="#prop_tgt:BUILD_WITH_INSTALL_RPATH"><b><code>BUILD_WITH_INSTALL_RPATH</code></b></a></li> <li><a href="#prop_tgt:CLEAN_DIRECT_OUTPUT"><b><code>CLEAN_DIRECT_OUTPUT</code></b></a></li> <li><a href="#prop_tgt:COMPILE_DEFINITIONS"><b><code>COMPILE_DEFINITIONS</code></b></a></li> <li><a href="#prop_tgt:COMPILE_DEFINITIONS_CONFIG"><b><code>COMPILE_DEFINITIONS_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:COMPILE_FLAGS"><b><code>COMPILE_FLAGS</code></b></a></li> <li><a href="#prop_tgt:DEBUG_POSTFIX"><b><code>DEBUG_POSTFIX</code></b></a></li> <li><a href="#prop_tgt:DEFINE_SYMBOL"><b><code>DEFINE_SYMBOL</code></b></a></li> <li><a href="#prop_tgt:ENABLE_EXPORTS"><b><code>ENABLE_EXPORTS</code></b></a></li> <li><a href="#prop_tgt:EXCLUDE_FROM_ALL"><b><code>EXCLUDE_FROM_ALL</code></b></a></li> <li><a href="#prop_tgt:EchoString"><b><code>EchoString</code></b></a></li> <li><a href="#prop_tgt:FRAMEWORK"><b><code>FRAMEWORK</code></b></a></li> <li><a href="#prop_tgt:Fortran_MODULE_DIRECTORY"><b><code>Fortran_MODULE_DIRECTORY</code></b></a></li> <li><a href="#prop_tgt:GENERATOR_FILE_NAME"><b><code>GENERATOR_FILE_NAME</code></b></a></li> <li><a href="#prop_tgt:HAS_CXX"><b><code>HAS_CXX</code></b></a></li> <li><a href="#prop_tgt:IMPLICIT_DEPENDS_INCLUDE_TRANSFORM"><b><code>IMPLICIT_DEPENDS_INCLUDE_TRANSFORM</code></b></a></li> <li><a href="#prop_tgt:IMPORTED"><b><code>IMPORTED</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_CONFIGURATIONS"><b><code>IMPORTED_CONFIGURATIONS</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_IMPLIB"><b><code>IMPORTED_IMPLIB</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_IMPLIB_CONFIG"><b><code>IMPORTED_IMPLIB_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LINK_DEPENDENT_LIBRARIES"><b><code>IMPORTED_LINK_DEPENDENT_LIBRARIES</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LINK_DEPENDENT_LIBRARIES_CONFIG"><b><code>IMPORTED_LINK_DEPENDENT_LIBRARIES_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LINK_INTERFACE_LIBRARIES"><b><code>IMPORTED_LINK_INTERFACE_LIBRARIES</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LINK_INTERFACE_LIBRARIES_CONFIG"><b><code>IMPORTED_LINK_INTERFACE_LIBRARIES_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LOCATION"><b><code>IMPORTED_LOCATION</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_LOCATION_CONFIG"><b><code>IMPORTED_LOCATION_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORTED_SONAME"><b><code>IMPORTED_SONAME</code></b></a></li> <li><a href="#prop_tgt:IMPORTED_SONAME_CONFIG"><b><code>IMPORTED_SONAME_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:IMPORT_PREFIX"><b><code>IMPORT_PREFIX</code></b></a></li> <li><a href="#prop_tgt:IMPORT_SUFFIX"><b><code>IMPORT_SUFFIX</code></b></a></li> <li><a href="#prop_tgt:INSTALL_NAME_DIR"><b><code>INSTALL_NAME_DIR</code></b></a></li> <li><a href="#prop_tgt:INSTALL_RPATH"><b><code>INSTALL_RPATH</code></b></a></li> <li><a href="#prop_tgt:INSTALL_RPATH_USE_LINK_PATH"><b><code>INSTALL_RPATH_USE_LINK_PATH</code></b></a></li> <li><a href="#prop_tgt:LIBRARY_OUTPUT_DIRECTORY"><b><code>LIBRARY_OUTPUT_DIRECTORY</code></b></a></li> <li><a href="#prop_tgt:LINKER_LANGUAGE"><b><code>LINKER_LANGUAGE</code></b></a></li> <li><a href="#prop_tgt:LINK_FLAGS"><b><code>LINK_FLAGS</code></b></a></li> <li><a href="#prop_tgt:LINK_FLAGS_CONFIG"><b><code>LINK_FLAGS_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:LINK_INTERFACE_LIBRARIES"><b><code>LINK_INTERFACE_LIBRARIES</code></b></a></li> <li><a href="#prop_tgt:LINK_INTERFACE_LIBRARIES_CONFIG"><b><code>LINK_INTERFACE_LIBRARIES_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:LINK_SEARCH_END_STATIC"><b><code>LINK_SEARCH_END_STATIC</code></b></a></li> <li><a href="#prop_tgt:LOCATION"><b><code>LOCATION</code></b></a></li> <li><a href="#prop_tgt:LOCATION_CONFIG"><b><code>LOCATION_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:MACOSX_BUNDLE"><b><code>MACOSX_BUNDLE</code></b></a></li> <li><a href="#prop_tgt:MACOSX_BUNDLE_INFO_PLIST"><b><code>MACOSX_BUNDLE_INFO_PLIST</code></b></a></li> <li><a href="#prop_tgt:MAP_IMPORTED_CONFIG_CONFIG"><b><code>MAP_IMPORTED_CONFIG_<CONFIG></code></b></a></li> <li><a href="#prop_tgt:OUTPUT_NAME"><b><code>OUTPUT_NAME</code></b></a></li> <li><a href="#prop_tgt:POST_INSTALL_SCRIPT"><b><code>POST_INSTALL_SCRIPT</code></b></a></li> <li><a href="#prop_tgt:PREFIX"><b><code>PREFIX</code></b></a></li> <li><a href="#prop_tgt:PRE_INSTALL_SCRIPT"><b><code>PRE_INSTALL_SCRIPT</code></b></a></li> <li><a href="#prop_tgt:PRIVATE_HEADER"><b><code>PRIVATE_HEADER</code></b></a></li> <li><a href="#prop_tgt:PUBLIC_HEADER"><b><code>PUBLIC_HEADER</code></b></a></li> <li><a href="#prop_tgt:RESOURCE"><b><code>RESOURCE</code></b></a></li> <li><a href="#prop_tgt:RUNTIME_OUTPUT_DIRECTORY"><b><code>RUNTIME_OUTPUT_DIRECTORY</code></b></a></li> <li><a href="#prop_tgt:SKIP_BUILD_RPATH"><b><code>SKIP_BUILD_RPATH</code></b></a></li> <li><a href="#prop_tgt:SOURCES"><b><code>SOURCES</code></b></a></li> <li><a href="#prop_tgt:SOVERSION"><b><code>SOVERSION</code></b></a></li> <li><a href="#prop_tgt:STATIC_LIBRARY_FLAGS"><b><code>STATIC_LIBRARY_FLAGS</code></b></a></li> <li><a href="#prop_tgt:SUFFIX"><b><code>SUFFIX</code></b></a></li> <li><a href="#prop_tgt:VERSION"><b><code>VERSION</code></b></a></li> <li><a href="#prop_tgt:WIN32_EXECUTABLE"><b><code>WIN32_EXECUTABLE</code></b></a></li> <li><a href="#prop_tgt:XCODE_ATTRIBUTE_an-attribute"><b><code>XCODE_ATTRIBUTE_<an-attribute></code></b></a></li></ul>
<ul>
<li>
***************
*** 909,912 ****
--- 960,970 ----
</li>
<li>
+ <a name="prop_tgt:IMPLICIT_DEPENDS_INCLUDE_TRANSFORM"><b><code>IMPLICIT_DEPENDS_INCLUDE_TRANSFORM</code></b></a>: Specify #include line transforms for dependencies in a target.<br>
+ <p>This property specifies rules to transform macro-like #include lines during implicit dependency scanning of C and C++ source files. The list of rules must be semicolon-separated with each entry of the form "A_MACRO(%)=value-with-%" (the % must be literal). During dependency scanning occurrences of A_MACRO(...) on #include lines will be replaced by the value given with the macro argument substituted for '%'. For example, the entry<br><pre> MYDIR(%)=<mydir/%><br></pre>
+ <p>will convert lines of the form<br><pre> #include MYDIR(myheader.h)<br></pre>
+ <p>to<br><pre> #include <mydir/myheader.h><br></pre>
+ <p>allowing the dependency to be followed.<br><p>This property applies to sources in the target on which it is set.
+ </li>
+ <li>
<a name="prop_tgt:IMPORTED"><b><code>IMPORTED</code></b></a>: Read-only indication of whether a target is IMPORTED.<br>
<p>The boolean value of this property is true for targets created with the IMPORTED option to add_executable or add_library. It is false for targets built within the project.
***************
*** 1014,1019 ****
<li>
<a name="prop_tgt:MACOSX_BUNDLE"><b><code>MACOSX_BUNDLE</code></b></a>: Build an executable as an application bundle on Mac OS X.<br>
! <p>When this property is set to true the executable when built on Mac OS X will be created as an application bundle. This makes it a GUI executable that can be launched from the Finder.<br><p>The bundle Info.plist file is generated automatically. The following target properties may be set to specify its content: MACOSX_BUNDLE_INFO_STRING<br><pre> MACOSX_BUNDLE_ICON_FILE<br> MACOSX_BUNDLE_GUI_IDENTIFIER<br> MACOSX_BUNDLE_LONG_VERSION_STRING<br> MACOSX_BUNDLE_BUNDLE_NAME<br> MACOSX_BUNDLE_SHORT_VERSION_STRING<br> MACOSX_BUNDLE_BUNDLE_VERSION<br> MACOSX_BUNDLE_COPYRIGHT<br></pre>
!
</li>
<li>
--- 1072,1081 ----
<li>
<a name="prop_tgt:MACOSX_BUNDLE"><b><code>MACOSX_BUNDLE</code></b></a>: Build an executable as an application bundle on Mac OS X.<br>
! <p>When this property is set to true the executable when built on Mac OS X will be created as an application bundle. This makes it a GUI executable that can be launched from the Finder. See the MACOSX_BUNDLE_INFO_PLIST target property for information about creation of the Info.plist file for the application bundle.
! </li>
! <li>
! <a name="prop_tgt:MACOSX_BUNDLE_INFO_PLIST"><b><code>MACOSX_BUNDLE_INFO_PLIST</code></b></a>: Specify a custom Info.plist template for a Mac OS X App Bundle.<br>
! <p>An executable target with MACOSX_BUNDLE enabled will be built as an application bundle on Mac OS X. By default its Info.plist file is created by configuring a template called MacOSXBundleInfo.plist.in located in the CMAKE_MODULE_PATH. This property specifies an alternative template file name which may be a full path.<br><p>The following target properties may be set to specify content to be configured into the file:<br><pre> MACOSX_BUNDLE_INFO_STRING<br> MACOSX_BUNDLE_ICON_FILE<br> MACOSX_BUNDLE_GUI_IDENTIFIER<br> MACOSX_BUNDLE_LONG_VERSION_STRING<br> MACOSX_BUNDLE_BUNDLE_NAME<br> MACOSX_BUNDLE_SHORT_VERSION_STRING<br> MACOSX_BUNDLE_BUNDLE_VERSION<br> MACOSX_BUNDLE_COPYRIGHT<br></pre>
! <p>CMake variables of the same name may be set to affect all targets in a directory that do not have each specific property set. If a custom Info.plist is specified by this property it may of course hard-code all the settings instead of using the target properties.
</li>
<li>
***************
*** 1322,1327 ****
</li>
<li>
! <a name="module:CPack"><b><code>CPack</code></b></a>: <br>
! <p>Default output files will be CPackConfig.cmake and CPackSourceConfig.cmake. This can be overwritten with CPACK_OUTPUT_CONFIG_FILE and CPACK_SOURCE_OUTPUT_CONFIG_FILE.
</li>
<li>
--- 1384,1467 ----
</li>
<li>
! <a name="module:CPack"><b><code>CPack</code></b></a>: Build binary and source package installers<br>
! <p><br><p>The CPack module generates binary and source installers in a variety of formats using the cpack program. Inclusion of the CPack module adds two new targets to the resulting makefiles, package and package_source, which build the binary and source installers, respectively. The generated binary installers contain everything installed via CMake's INSTALL command (and the deprecated INSTALL_FILES, INSTALL_PROGRAMS, and INSTALL_TARGETS commands).<br><p>For certain kinds of binary installers (including the graphical installers on Mac OS X and Windows), CPack generates installers that allow users to select individual application components to install. The contents of each of the components are identified by the COMPONENT argument of CMake's INSTALL command. These components can be annotated with user-friendly names and descriptions, inter-component dependencies, etc., and grouped in various ways to customize the resulting installer. See the cpack_add_* commands, described below, for more information about component-specific installations.<br><p>Before including the CPack module, there are a variety of variables that can be set to customize the resulting installers. The most commonly-used variables are:<br><pre> CPACK_PACKAGE_NAME - The name of the package (or application). If<br> not specified, defaults to the project name.<br></pre>
! <p><br><pre> CPACK_PACKAGE_VENDOR - The name of the package vendor (e.g.,<br> "Kitware").<br></pre>
! <p><br><pre> CPACK_PACKAGE_VERSION_MAJOR - Package major Version<br></pre>
! <p><br><pre> CPACK_PACKAGE_VERSION_MINOR - Package minor Version<br></pre>
! <p><br><pre> CPACK_PACKAGE_VERSION_PATCH - Package patch Version<br></pre>
! <p><br><pre> CPACK_PACKAGE_DESCRIPTION_FILE - A text file used to describe the<br> project. Used, for example, the introduction screen of a<br> CPack-generated Windows installer to describe the project.<br></pre>
! <p><br><pre> CPACK_PACKAGE_DESCRIPTION_SUMMARY - Short description of the<br> project (only a few words).<br></pre>
! <p><br><pre> CPACK_PACKAGE_FILE_NAME - The name of the package file to generate,<br> not including the extension. For example, cmake-2.6.1-Linux-i686.<br></pre>
! <p><br><pre> CPACK_PACKAGE_INSTALL_DIRECTORY - Installation directory on the<br> target system, e.g., "CMake 2.5".<br></pre>
! <p><br><pre> CPACK_RESOURCE_FILE_LICENSE - License file for the project, which<br> will typically be displayed to the user (often with an explicit<br> "Accept" button, for graphical installers) prior to installation.<br></pre>
! <p><br><pre> CPACK_RESOURCE_FILE_README - ReadMe file for the project, which<br> typically describes in some detail<br></pre>
! <p><br><pre> CPACK_RESOURCE_FILE_WELCOME - Welcome file for the project, which<br> welcomes users to this installer. Typically used in the graphical<br> installers on Windows and Mac OS X.<br></pre>
! <p><br><pre> CPACK_MONOLITHIC_INSTALL - Disables the component-based <br> installation mechanism, so that all components are always installed.<br></pre>
! <p><br><pre> CPACK_GENERATOR - List of CPack generators to use. If not<br> specified, CPack will create a set of options (e.g.,<br> CPACK_BINARY_NSIS) allowing the user to enable/disable individual<br> generators.<br></pre>
! <p><br><pre> CPACK_OUTPUT_CONFIG_FILE - The name of the CPack configuration file<br> for binary installers that will be generated by the CPack<br> module. Defaults to CPackConfig.cmake.<br></pre>
! <p><br><pre> CPACK_PACKAGE_EXECUTABLES - Lists each of the executables along<br> with a text label, to be used to create Start Menu shortcuts on<br> Windows. For example, setting this to the list ccmake;CMake will<br> create a shortcut named "CMake" that will execute the installed<br> executable ccmake.<br></pre>
! <p><br><pre> CPACK_STRIP_FILES - List of files to be stripped. Starting with<br> CMake 2.6.0 CPACK_STRIP_FILES will be a boolean variable which<br> enables stripping of all files (a list of files evaluates to TRUE<br> in CMake, so this change is compatible).<br></pre>
! <p><br><p>The following CPack variables are specific to source packages, and will not affect binary packages:<br><pre> CPACK_SOURCE_PACKAGE_FILE_NAME - The name of the source package,<br> e.g., cmake-2.6.1<br></pre>
! <p><br><pre> CPACK_SOURCE_STRIP_FILES - List of files in the source tree that<br> will be stripped. Starting with CMake 2.6.0<br> CPACK_SOURCE_STRIP_FILES will be a boolean variable which enables<br> stripping of all files (a list of files evaluates to TRUE in CMake,<br> so this change is compatible).<br></pre>
! <p><br><pre> CPACK_SOURCE_GENERATOR - List of generators used for the source<br> packages. As with CPACK_GENERATOR, if this is not specified then<br> CPack will create a set of options (e.g., CPACK_SOURCE_ZIP)<br> allowing users to select which packages will be generated.<br></pre>
! <p><br><pre> CPACK_SOURCE_OUTPUT_CONFIG_FILE - The name of the CPack<br> configuration file for source installers that will be generated by<br> the CPack module. Defaults to CPackSourceConfig.cmake.<br></pre>
! <p><br><pre> CPACK_SOURCE_IGNORE_FILES - Pattern of files in the source tree<br> that won't be packaged when building a source package. This is a<br> list of patterns, e.g., /CVS/;/\\.svn/;\\.swp$;\\.#;/#;.*~;cscope.*<br></pre>
! <p><br><p>The following variables are specific to the graphical installers built on Windows using the Nullsoft Installation System.<br><pre> CPACK_PACKAGE_INSTALL_REGISTRY_KEY - Registry key used when<br> installing this project.<br></pre>
! <p><br><pre> CPACK_NSIS_MUI_ICON - The icon file (.ico) for the generated<br> install program.<br></pre>
! <p><br><pre> CPACK_NSIS_MUI_UNIICON - The icon file (.ico) for the generated<br> uninstall program.<br></pre>
! <p><br><pre> CPACK_PACKAGE_ICON - A branding image that will be displayed inside<br> the installer.<br></pre>
! <p><br><pre> CPACK_NSIS_EXTRA_INSTALL_COMMANDS - Extra NSIS commands that will<br> be added to the install Section.<br></pre>
! <p><br><pre> CPACK_NSIS_EXTRA_UNINSTALL_COMMANDS - Extra NSIS commands that will<br> be added to the uninstall Section.<br></pre>
! <p><br><pre> CPACK_NSIS_COMPRESSOR - The arguments that will be passed to the<br> NSIS SetCompressor command.<br></pre>
! <p><br><pre> CPACK_NSIS_MODIFY_PATH - If this is set to "ON", then an extra page<br> will appear in the installer that will allow the user to choose<br> whether the program directory should be added to the system PATH<br> variable.<br></pre>
! <p><br><pre> CPACK_NSIS_DISPLAY_NAME - The title displayed at the top of the<br> installer.<br></pre>
! <p><br><pre> CPACK_NSIS_INSTALLED_ICON_NAME - A path to the executable that<br> contains the installer icon.<br></pre>
! <p><br><pre> CPACK_NSIS_HELP_LINK - URL to a web site providing assistance in<br> installing your application.<br></pre>
! <p><br><pre> CPACK_NSIS_URL_INFO_ABOUT - URL to a web site providing more<br> information about your application.<br></pre>
! <p><br><pre> CPACK_NSIS_CONTACT - Contact information for questions and comments<br> about the installation process.<br></pre>
! <p><br><pre> CPACK_NSIS_CREATE_ICONS_EXTRA - Additional NSIS commands for<br> creating start menu shortcuts.<br></pre>
! <p><br><pre> CPACK_NSIS_DELETE_ICONS_EXTRA -Additional NSIS commands to<br> uninstall start menu shortcuts.<br></pre>
! <p><br><p>The following variable is specific to installers build on Mac OS X using PackageMaker:<br><pre> CPACK_OSX_PACKAGE_VERSION - The version of Mac OS X that the<br> resulting PackageMaker archive should be compatible<br> with. Different versions of Mac OS X support different<br> features. For example, CPack can only build component-based<br> installers for Mac OS X 10.4 or newer, and can only build<br> installers that download component son-the-fly for Mac OS X 10.5<br> or newer. If left blank, this value will be set to the minimum<br> version of Mac OS X that supports the requested features. Set this<br> variable to some value (e.g., 10.4) only if you want to guarantee<br> that your installer will work on that version of Mac OS X, and<br> don't mind missing extra features available in the installer<br> shipping with later versions of Mac OS X.<br></pre>
! <p><br><p>The following variables are for advanced uses of CPack:<br><pre> CPACK_CMAKE_GENERATOR - What CMake generator should be used if the<br> project is CMake project. Defaults to the value of CMAKE_GENERATOR;<br> few users will want to change this setting.<br></pre>
! <p><br><pre> CPACK_INSTALL_CMAKE_PROJECTS - List of four values that specify<br> what project to install. The four values are: Build directory,<br> Project Name, Project Component, Directory. If omitted, CPack will<br> build an installer that installers everything.<br></pre>
! <p><br><pre> CPACK_SYSTEM_NAME - System name, defaults to the value of<br> ${CMAKE_SYSTEM_NAME}.<br></pre>
! <p><br><pre> CPACK_PACKAGE_VERSION - Package full version, used internally. By<br> default, this is built from CPACK_PACKAGE_VERSION_MAJOR,<br> CPACK_PACKAGE_VERSION_MINOR, and CPACK_PACKAGE_VERSION_PATCH.<br></pre>
! <p><br><pre> CPACK_TOPLEVEL_TAG - Directory for the installed files.<br></pre>
! <p><br><pre> CPACK_INSTALL_COMMANDS - Extra commands to install components.<br></pre>
! <p><br><pre> CPACK_INSTALL_DIRECTORIES - Extra directories to install.<br></pre>
! <p><br><p>Component-specific installation allows users to select specific sets of components to install during the install process. Installation components are identified by the COMPONENT argument of CMake's INSTALL commands, and should be further described by the following CPack commands:<br><pre> cpack_add_component - Describes a CPack installation component<br> named by the COMPONENT argument to a CMake INSTALL command.<br></pre>
! <p><br><pre> cpack_add_component(compname<br> [DISPLAY_NAME name]<br> [DESCRIPTION description]<br> [HIDDEN | REQUIRED | DISABLED ]<br> [GROUP group]<br> [DEPENDS comp1 comp2 ... ]<br> [INSTALL_TYPES type1 type2 ... ]<br> [DOWNLOADED]<br> [ARCHIVE_FILE filename])<br></pre>
! <p><br><pre> The cmake_add_component command describes an installation<br> component, which the user can opt to install or remove as part of<br> the graphical installation process. compname is the name of the<br> component, as provided to the COMPONENT argument of one or more<br> CMake INSTALL commands.<br></pre>
! <p><br><pre> DISPLAY_NAME is the displayed name of the component, used in<br> graphical installers to display the component name. This value can<br> be any string.<br></pre>
! <p><br><pre> DESCRIPTION is an extended description of the component, used in<br> graphical installers to give the user additional information about<br> the component. Descriptions can span multiple lines using "\n" as<br> the line separator. Typically, these descriptions should be no<br> more than a few lines long.<br></pre>
! <p><br><pre> HIDDEN indicates that this component will be hidden in the<br> graphical installer, so that the user cannot directly change<br> whether it is installed or not.<br></pre>
! <p><br><pre> REQUIRED indicates that this component is required, and therefore<br> will always be installed. It will be visible in the graphical<br> installer, but it cannot be unselected. (Typically, required<br> components are shown greyed out).<br></pre>
! <p><br><pre> DISABLED indicates that this component should be disabled<br> (unselected) by default. The user is free to select this component<br> for installation, unless it is also HIDDEN.<br></pre>
! <p><br><pre> DEPENDS lists the components on which this component depends. If<br> this component is selected, then each of the components listed<br> must also be selected. The dependency information is encoded<br> within the installer itself, so that users cannot install<br> inconsitent sets of components.<br></pre>
! <p><br><pre> GROUP names the component group of which this component is a<br> part. If not provided, the component will be a standalone<br> component, not part of any component group. Component groups are<br> described with the cpack_add_component_group command, detailed<br> below.<br></pre>
! <p><br><pre> INSTALL_TYPES lists the installation types of which this component<br> is a part. When one of these installations types is selected, this<br> component will automatically be selected. Installation types are<br> described with the cpack_add_install_type command, detailed below.<br></pre>
! <p><br><pre> DOWNLOADED indicates that this component should be downloaded<br> on-the-fly by the installer, rather than packaged in with the<br> installer itself. For more information, see the cpack_configure_downloads<br> command.<br></pre>
! <p><br><pre> ARCHIVE_FILE provides a name for the archive file created by CPack<br> to be used for downloaded components. If not supplied, CPack will<br> create a file with some name based on CPACK_PACKAGE_FILE_NAME and<br> the name of the component. See cpack_configure_downloads for more<br> information.<br></pre>
! <p><br><pre> cpack_add_component_group - Describes a group of related CPack<br> installation components.<br></pre>
! <p><br><pre> cpack_add_component_group(groupname<br> [DISPLAY_NAME name]<br> [DESCRIPTION description]<br> [PARENT_GROUP parent]<br> [EXPANDED]<br> [BOLD_TITLE])<br></pre>
! <p><br><pre> The cpack_add_component_group describes a group of installation<br> components, which will be placed together within the listing of<br> options. Typically, component groups allow the user to<br> select/deselect all of the components within a single group via a<br> single group-level option. Use component groups to reduce the<br> complexity of installers with many options. groupname is an<br> arbitrary name used to identify the group in the GROUP argument of<br> the cpack_add_component command, which is used to place a<br> component in a group. The name of the group must not conflict with<br> the name of any component.<br></pre>
! <p><br><pre> DISPLAY_NAME is the displayed name of the component group, used in<br> graphical installers to display the component group name. This<br> value can be any string.<br></pre>
! <p><br><pre> DESCRIPTION is an extended description of the component group,<br> used in graphical installers to give the user additional<br> information about the components within that group. Descriptions<br> can span multiple lines using "\n" as the line<br> separator. Typically, these descriptions should be no more than a<br> few lines long.<br></pre>
! <p><br><pre> PARENT_GROUP, if supplied, names the parent group of this group. <br> Parent groups are used to establish a hierarchy of groups, <br> providing an arbitrary hierarchy of groups.<br></pre>
! <p><br><pre> EXPANDED indicates that, by default, the group should show up as<br> "expanded", so that the user immediately sees all of the<br> components within the group. Otherwise, the group will initially<br> show up as a single entry.<br></pre>
! <p><br><pre> BOLD_TITLE indicates that the group title should appear in bold,<br> to call the user's attention to the group.<br></pre>
! <p><br><pre> cpack_add_install_type - Add a new installation type containing a<br> set of predefined component selections to the graphical installer.<br> <br> cpack_add_install_type(typename<br> [DISPLAY_NAME name]) <br></pre>
! <p><br><pre> The cpack_add_install_type command identifies a set of preselected<br> components that represents a common use case for an<br> application. For example, a "Developer" install type might include<br> an application along with its header and library files, while an<br> "End user" install type might just include the application's<br> executable. Each component identifies itself with one or more<br> install types via the INSTALL_TYPES argument to<br> cpack_add_component.<br></pre>
! <p><br><pre> DISPLAY_NAME is the displayed name of the install type, which will<br> typically show up in a drop-down box within a graphical<br> installer. This value can be any string.<br></pre>
! <p><br><pre> cpack_configure_downloads - Configure CPack to download selected<br> components on-the-fly as part of the installation process.<br></pre>
! <p><br><pre> cpack_configure_downloads(site<br> [UPLOAD_DIRECTORY dirname]<br> [ALL]<br> [ADD_REMOVE|NO_ADD_REMOVE])<br></pre>
! <p><br><pre> The cpack_configure_downloads command configures installation-time<br> downloads of selected components. For each downloadable component,<br> CPack will create an archive containing the contents of that<br> component, which should be uploaded to the given site. When the<br> user selects that component for installation, the installer will<br> download and extract the component in place. This feature is<br> useful for creating small installers that only download the<br> requested components, saving bandwidth. Additionally, the<br> installers are small enough that they will be installed as part of<br> the normal installation process, and the "Change" button in<br> Windows Add/Remove Programs control panel will allow one to add or<br> remove parts of the application after the original<br> installation. On Windows, the downloaded-components functionality<br> requires the ZipDLL plug-in for NSIS, available at:<br></pre>
! <p><br><pre> <a href="http://nsis.sourceforge.net/ZipDLL_plug-in">http://nsis.sourceforge.net/ZipDLL_plug-in</a><br></pre>
! <p><br><pre> On Mac OS X, installers that download components on-the-fly can<br> only be built and installed on system using Mac OS X 10.5 or<br> later.<br></pre>
! <p><br><pre> The site argument is a URL where the archives for downloadable <br> components will reside, e.g., <a href="http://www.cmake.org/files/2.6.1/installer/">http://www.cmake.org/files/2.6.1/installer/</a><br> All of the archives produced by CPack should be uploaded to that location.<br></pre>
! <p><br><pre> UPLOAD_DIRECTORY is the local directory where CPack will create the <br> various archives for each of the components. The contents of this<br> directory should be uploaded to a location accessible by the URL given<br> in the site argument. If omitted, CPack will use the directory CPackUploads<br> inside the CMake binary directory to store the generated archives.<br></pre>
! <p><br><pre> The ALL flag indicates that all components be downloaded. Otherwise, only <br> those components explicitly marked as DOWNLOADED or that have a specified <br> ARCHIVE_FILE will be downloaded. Additionally, the ALL option implies<br> ADD_REMOVE (unless NO_ADD_REMOVE is specified).<br></pre>
! <p><br><pre> ADD_REMOVE indicates that CPack should install a copy of the installer<br> that can be called from Windows' Add/Remove Programs dialog (via the <br> "Modify" button) to change the set of installed components. NO_ADD_REMOVE<br> turns off this behavior. This option is ignored on Mac OS X.<br></pre>
!
</li>
<li>
***************
*** 1372,1376 ****
<p>CHECK_FORTRAN_FUNCTION_EXISTS(FUNCTION VARIABLE)<br><pre> FUNCTION - the name of the Fortran function<br> VARIABLE - variable to store the result<br></pre>
<p><br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
! <p><br>
</li>
<li>
--- 1512,1516 ----
<p>CHECK_FORTRAN_FUNCTION_EXISTS(FUNCTION VARIABLE)<br><pre> FUNCTION - the name of the Fortran function<br> VARIABLE - variable to store the result<br></pre>
<p><br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
!
</li>
<li>
***************
*** 1458,1463 ****
<li>
<a name="module:FindBLAS"><b><code>FindBLAS</code></b></a>: Find BLAS library<br>
! <p>This module finds an installed fortran library that implements the BLAS linear-algebra interface (see <a href="http://www.netlib.org/blas/">http://www.netlib.org/blas/</a>). The list of libraries searched for is taken from the autoconf macro file, acx_blas.m4 (distributed at <a href="http://ac-archive.sourceforge.net/ac-archive/acx_blas.html">http://ac-archive.sourceforge.net/ac-archive/acx_blas.html</a>).<br><p>This module sets the following variables:<br><pre> BLAS_FOUND - set to true if a library implementing the BLAS interface<br> is found<br> BLAS_LINKER_FLAGS - uncached list of required linker flags (excluding -l<br> and -L).<br> BLAS_LIBRARIES - uncached list of libraries (using full path name) to <br> link against to use BLAS<br> BLAS95_LIBRARIES - uncached list of libraries (using full path name) # to link against to use BLAS95 interface<br></pre>
! <p><br>
</li>
<li>
--- 1598,1603 ----
<li>
<a name="module:FindBLAS"><b><code>FindBLAS</code></b></a>: Find BLAS library<br>
! <p>This module finds an installed fortran library that implements the BLAS linear-algebra interface (see <a href="http://www.netlib.org/blas/">http://www.netlib.org/blas/</a>). The list of libraries searched for is taken from the autoconf macro file, acx_blas.m4 (distributed at <a href="http://ac-archive.sourceforge.net/ac-archive/acx_blas.html">http://ac-archive.sourceforge.net/ac-archive/acx_blas.html</a>).<br><p>This module sets the following variables:<br><pre> BLAS_FOUND - set to true if a library implementing the BLAS interface<br> is found<br> BLAS_LINKER_FLAGS - uncached list of required linker flags (excluding -l<br> and -L).<br> BLAS_LIBRARIES - uncached list of libraries (using full path name) to<br> link against to use BLAS<br> BLAS95_LIBRARIES - uncached list of libraries (using full path name)<br> to link against to use BLAS95 interface<br> BLAS95_FOUND - set to true if a library implementing the BLAS f95 interface<br> is found<br> BLA_STATIC if set on this determines what kind of linkage we do (static)<br> BLA_VENDOR if set checks only the specified vendor, if not set checks<br> all the posibilities<br> BLA_F95 if set on tries to find the f95 interfaces for BLAS/LAPACK<br></pre>
! <p>######### ## List of vendors (BLA_VENDOR) valid in this module # ATLAS, PhiPACK,CXML,DXML,SunPerf,SCSL,SGIMATH,IBMESSL,Intel10_32 (intel mkl v10 32 bit),Intel10_64lp (intel mkl v10 64 bit,lp thread model, lp64 model), # Intel( older versions of mkl 32 and 64 bit), ACML,Apple, NAS, Generic C/CXX should be enabled to use Intel mkl
</li>
<li>
***************
*** 1469,1473 ****
<a name="module:FindBoost"><b><code>FindBoost</code></b></a>: Try to find Boost include dirs and libraries<br>
<p>Usage of this module as follows:<br><pre> SET(Boost_USE_STATIC_LIBS ON)<br> SET(Boost_USE_MULTITHREAD OFF)<br> FIND_PACKAGE( Boost 1.34.1 COMPONENTS date_time filesystem iostreams ... )<br></pre>
! <p><br><p>The Boost_ADDITIONAL_VERSIONS variable can be used to specify a list of boost version numbers that should be taken into account when searching for the libraries. Unfortunately boost puts the version number into the actual filename for the libraries, so this might be needed in the future when new Boost versions are released.<br><p>Currently this module searches for the following version numbers: 1.33, 1.33.0, 1.33.1, 1.34, 1.34.0, 1.34.1, 1.35, 1.35.0, 1.35.1, 1.36.0, 1.36.1<br><p>The components list needs to be the actual names of boost libraries, that is the part of the actual library files that differ on different libraries. So its "date_time" for "libboost_date_time...". Anything else will result in errors<br><p>You can provide a minimum version number that should be used. If you provide this version number and specify the REQUIRED attribute, this module will fail if it can't find the specified or a later version. If you specify a version number this is automatically put into the considered list of version numbers and thus doesn't need to be specified in the Boost_ADDITIONAL_VERSIONS variable<br><p>Variables used by this module, they can change the default behaviour and need to be set before calling find_package:<br><pre> Boost_USE_MULTITHREAD Can be set to OFF to use the non-multithreaded<br> boost libraries. Defaults to ON.<br> Boost_USE_STATIC_LIBS Can be set to ON to force the use of the static<br> boost libraries. Defaults to OFF.<br> Boost_ADDITIONAL_VERSIONS A list of version numbers to use for searching<br> the boost include directory. The default list<br> of version numbers is:<br> 1.33, 1.33.0, 1.33.1, 1.34, 1.34.0, 1.34.1, <br> 1.35, 1.35.0, 1.35.1, 1.36.0, 1.36.1<br> If you want to look for an older or newer<br> version set this variable to a list of<br> strings, where each string contains a number, i.e.<br> SET(Boost_ADDITIONAL_VERSIONS "0.99.0" "1.35.0")<br> BOOST_ROOT Preferred installation prefix for searching for Boost,<br> set this if the module has problems finding the proper Boost installation<br> BOOST_INCLUDEDIR Set this to the include directory of Boost, if the<br> module has problems finding the proper Boost installation<br> BOOST_LIBRARYDIR Set this to the lib directory of Boost, if the<br> module has problems finding the proper Boost installation<br></pre>
<p><br><pre> The last three variables are available also as environment variables<br></pre>
<p><br><p><br><p>Variables defined by this module:<br><pre> Boost_FOUND System has Boost, this means the include dir was found,<br> as well as all the libraries specified in the COMPONENTS list<br> Boost_INCLUDE_DIRS Boost include directories, not cached<br> Boost_INCLUDE_DIR This is almost the same as above, but this one is cached and may be<br> modified by advanced users<br> Boost_LIBRARIES Link these to use the Boost libraries that you specified, not cached<br> Boost_LIBRARY_DIRS The path to where the Boost library files are.<br> Boost_VERSION The version number of the boost libraries that have been found,<br> same as in version.hpp from Boost<br> Boost_LIB_VERSION The version number in filename form as its appended to the library filenames<br> Boost_MAJOR_VERSION major version number of boost<br> Boost_MINOR_VERSION minor version number of boost<br> Boost_SUBMINOR_VERSION subminor version number of boost<br> Boost_LIB_DIAGNOSTIC_DEFINITIONS Only set on windows. Can be used with add_definitions <br> to print diagnostic information about the automatic <br> linking done on windows.<br></pre>
--- 1609,1613 ----
<a name="module:FindBoost"><b><code>FindBoost</code></b></a>: Try to find Boost include dirs and libraries<br>
<p>Usage of this module as follows:<br><pre> SET(Boost_USE_STATIC_LIBS ON)<br> SET(Boost_USE_MULTITHREAD OFF)<br> FIND_PACKAGE( Boost 1.34.1 COMPONENTS date_time filesystem iostreams ... )<br></pre>
! <p><br><p>The Boost_ADDITIONAL_VERSIONS variable can be used to specify a list of boost version numbers that should be taken into account when searching for the libraries. Unfortunately boost puts the version number into the actual filename for the libraries, so this might be needed in the future when new Boost versions are released.<br><p>Currently this module searches for the following version numbers: 1.33, 1.33.0, 1.33.1, 1.34, 1.34.0, 1.34.1, 1.35, 1.35.0, 1.35.1, 1.36, 1.36.0, 1.36.1<br><p>The components list needs to be the actual names of boost libraries, that is the part of the actual library files that differ on different libraries. So its "date_time" for "libboost_date_time...". Anything else will result in errors<br><p>You can provide a minimum version number that should be used. If you provide this version number and specify the REQUIRED attribute, this module will fail if it can't find the specified or a later version. If you specify a version number this is automatically put into the considered list of version numbers and thus doesn't need to be specified in the Boost_ADDITIONAL_VERSIONS variable<br><p>Variables used by this module, they can change the default behaviour and need to be set before calling find_package:<br><pre> Boost_USE_MULTITHREAD Can be set to OFF to use the non-multithreaded<br> boost libraries. Defaults to ON.<br> Boost_USE_STATIC_LIBS Can be set to ON to force the use of the static<br> boost libraries. Defaults to OFF.<br> Boost_ADDITIONAL_VERSIONS A list of version numbers to use for searching<br> the boost include directory. The default list<br> of version numbers is:<br> 1.33, 1.33.0, 1.33.1, 1.34, 1.34.0, 1.34.1, <br> 1.35, 1.35.0, 1.35.1, 1.36, 1.36.0, 1.36.1<br> If you want to look for an older or newer<br> version set this variable to a list of<br> strings, where each string contains a number, i.e.<br> SET(Boost_ADDITIONAL_VERSIONS "0.99.0" "1.35.0")<br> BOOST_ROOT or BOOSTROOT Preferred installation prefix for searching for Boost,<br> set this if the module has problems finding the proper Boost installation<br> BOOST_INCLUDEDIR Set this to the include directory of Boost, if the<br> module has problems finding the proper Boost installation<br> BOOST_LIBRARYDIR Set this to the lib directory of Boost, if the<br> module has problems finding the proper Boost installation<br></pre>
<p><br><pre> The last three variables are available also as environment variables<br></pre>
<p><br><p><br><p>Variables defined by this module:<br><pre> Boost_FOUND System has Boost, this means the include dir was found,<br> as well as all the libraries specified in the COMPONENTS list<br> Boost_INCLUDE_DIRS Boost include directories, not cached<br> Boost_INCLUDE_DIR This is almost the same as above, but this one is cached and may be<br> modified by advanced users<br> Boost_LIBRARIES Link these to use the Boost libraries that you specified, not cached<br> Boost_LIBRARY_DIRS The path to where the Boost library files are.<br> Boost_VERSION The version number of the boost libraries that have been found,<br> same as in version.hpp from Boost<br> Boost_LIB_VERSION The version number in filename form as its appended to the library filenames<br> Boost_MAJOR_VERSION major version number of boost<br> Boost_MINOR_VERSION minor version number of boost<br> Boost_SUBMINOR_VERSION subminor version number of boost<br> Boost_LIB_DIAGNOSTIC_DEFINITIONS Only set on windows. Can be used with add_definitions <br> to print diagnostic information about the automatic <br> linking done on windows.<br></pre>
***************
*** 1586,1596 ****
</li>
<li>
! <a name="module:FindImageMagick"><b><code>FindImageMagick</code></b></a>: Find Image Magick<br>
! <p>This module finds if ImageMagick tools are installed and determines where the executables are. This code sets the following variables:<br><pre> IMAGEMAGICK_CONVERT_EXECUTABLE = <br> the full path to the 'convert' utility <br> IMAGEMAGICK_MOGRIFY_EXECUTABLE = <br> the full path to the 'mogrify' utility <br> IMAGEMAGICK_IMPORT_EXECUTABLE = <br> the full path to the 'import' utility <br> IMAGEMAGICK_MONTAGE_EXECUTABLE = <br> the full path to the 'montage' utility <br> IMAGEMAGICK_COMPOSITE_EXECUTABLE = <br> the full path to the 'composite' utility <br></pre>
! <p><br>
</li>
<li>
<a name="module:FindJNI"><b><code>FindJNI</code></b></a>: Find JNI java libraries.<br>
! <p>This module finds if Java is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> <br> JAVA_AWT_LIB_PATH = the path to the jawt library<br> JAVA_JVM_LIB_PATH = the path to the jvm library<br> JAVA_INCLUDE_PATH = the include path to jni.h<br> JAVA_INCLUDE_PATH2 = the include path to jni_md.h<br> JAVA_AWT_INCLUDE_PATH = the include path to jawt.h<br></pre>
<p><br>
</li>
--- 1726,1740 ----
</li>
<li>
! <a name="module:FindImageMagick"><b><code>FindImageMagick</code></b></a>: Find the ImageMagick binary suite.<br>
! <p>This module will search for a set of ImageMagick tools specified as components in the FIND_PACKAGE call. Typical components include, but are not limited to (future versions of ImageMagick might have additional components not listed here):<br><pre> animate<br> compare<br> composite<br> conjure<br> convert<br> display<br> identify<br> import<br> mogrify<br> montage<br> stream<br></pre>
! <p><br><p>If no component is specified in the FIND_PACKAGE call, then it only searches for the ImageMagick executable directory. This code defines the following variables:<br><pre> ImageMagick_FOUND - TRUE if all components are found.<br> ImageMagick_EXECUTABLE_DIR - Full path to executables directory.<br> ImageMagick_<component>_FOUND - TRUE if <component> is found.<br> ImageMagick_<component>_EXECUTABLE - Full path to <component> executable.<br></pre>
! <p><br><p>There are also components for the following ImageMagick APIs:<br><pre> Magick++<br> MagickWand<br> Magick<br></pre>
! <p><br><p>For these components the following variables are set:<br><pre> ImageMagick_FOUND - TRUE if all components are found.<br> ImageMagick_INCLUDE_DIRS - Full paths to all include dirs.<br> ImageMagick_LIBRARIES - Full paths to all libraries.<br> ImageMagick_<component>_FOUND - TRUE if <component> is found.<br> ImageMagick_<component>_INCLUDE_DIRS - Full path to <component> include dirs.<br> ImageMagick_<component>_LIBRARIES - Full path to <component> libraries.<br></pre>
! <p><br><p>Example Usages:<br><pre> FIND_PACKAGE(ImageMagick)<br> FIND_PACKAGE(ImageMagick COMPONENTS convert)<br> FIND_PACKAGE(ImageMagick COMPONENTS convert mogrify display)<br> FIND_PACKAGE(ImageMagick COMPONENTS Magick++)<br> FIND_PACKAGE(ImageMagick COMPONENTS Magick++ convert)<br></pre>
! <p><br><p>Note that the standard FIND_PACKAGE features are supported (i.e., QUIET, REQUIRED, etc.).
</li>
<li>
<a name="module:FindJNI"><b><code>FindJNI</code></b></a>: Find JNI java libraries.<br>
! <p>This module finds if Java is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> <br> JNI_INCLUDE_DIRS = the include dirs to use<br> JNI_LIBRARIES = the libraries to use<br> JAVA_AWT_LIBRARY = the path to the jawt library<br> JAVA_JVM_LIBRARY = the path to the jvm library<br> JAVA_INCLUDE_PATH = the include path to jni.h<br> JAVA_INCLUDE_PATH2 = the include path to jni_md.h<br> JAVA_AWT_INCLUDE_PATH = the include path to jawt.h<br></pre>
<p><br>
</li>
***************
*** 1634,1639 ****
<li>
<a name="module:FindLAPACK"><b><code>FindLAPACK</code></b></a>: Find LAPACK library<br>
! <p>This module finds an installed fortran library that implements the LAPACK linear-algebra interface (see <a href="http://www.netlib.org/lapack/">http://www.netlib.org/lapack/</a>).<br><p>The approach follows that taken for the autoconf macro file, acx_lapack.m4 (distributed at <a href="http://ac-archive.sourceforge.net/ac-archive/acx_lapack.html">http://ac-archive.sourceforge.net/ac-archive/acx_lapack.html</a>).<br><p>This module sets the following variables:<br><pre> LAPACK_FOUND - set to true if a library implementing the LAPACK interface<br> is found<br> LAPACK_LINKER_FLAGS - uncached list of required linker flags (excluding -l<br> and -L).<br> LAPACK_LIBRARIES - uncached list of libraries (using full path name) to <br> link against to use LAPACK<br> LAPACK95_LIBRARIES - uncached list of libraries (using full path name) to <br> link against to use LAPACK95<br></pre>
!
</li>
<li>
--- 1778,1783 ----
<li>
<a name="module:FindLAPACK"><b><code>FindLAPACK</code></b></a>: Find LAPACK library<br>
! <p>This module finds an installed fortran library that implements the LAPACK linear-algebra interface (see <a href="http://www.netlib.org/lapack/">http://www.netlib.org/lapack/</a>).<br><p>The approach follows that taken for the autoconf macro file, acx_lapack.m4 (distributed at <a href="http://ac-archive.sourceforge.net/ac-archive/acx_lapack.html">http://ac-archive.sourceforge.net/ac-archive/acx_lapack.html</a>).<br><p>This module sets the following variables:<br><pre> LAPACK_FOUND - set to true if a library implementing the LAPACK interface<br> is found<br> LAPACK_LINKER_FLAGS - uncached list of required linker flags (excluding -l<br> and -L).<br> LAPACK_LIBRARIES - uncached list of libraries (using full path name) to<br> link against to use LAPACK<br> LAPACK95_LIBRARIES - uncached list of libraries (using full path name) to<br> link against to use LAPACK95<br> LAPACK95_FOUND - set to true if a library implementing the LAPACK f95<br> interface is found<br> BLA_STATIC if set on this determines what kind of linkage we do (static)<br> BLA_VENDOR if set checks only the specified vendor, if not set checks<br> all the posibilities<br> BLA_F95 if set on tries to find the f95 interfaces for BLAS/LAPACK<br></pre>
! <p>## List of vendors (BLA_VENDOR) valid in this module # Intel(mkl), ACML,Apple, NAS, Generic
</li>
<li>
***************
*** 1880,1884 ****
<p>If the command line client executable is found the macro<br><pre> Subversion_WC_INFO(<dir> <var-prefix>)<br></pre>
<p>is defined to extract information of a subversion working copy at a given location. The macro defines the following variables:<br><pre> <var-prefix>_WC_URL - url of the repository (at <dir>)<br> <var-prefix>_WC_ROOT - root url of the repository<br> <var-prefix>_WC_REVISION - current revision<br> <var-prefix>_WC_LAST_CHANGED_AUTHOR - author of last commit<br> <var-prefix>_WC_LAST_CHANGED_DATE - date of last commit<br> <var-prefix>_WC_LAST_CHANGED_REV - revision of last commit<br> <var-prefix>_WC_LAST_CHANGED_LOG - last log of base revision<br> <var-prefix>_WC_INFO - output of command `svn info <dir>'<br></pre>
! <p>Example usage:<br><pre> FIND_PACKAGE(Subversion)<br> IF(Subversion_FOUND)<br> Subversion_WC_INFO(${PROJECT_SOURCE_DIR} Project)<br> MESSAGE("Current revision is ${Project_WC_REVISION}")<br> ENDIF(Subversion_FOUND)<br></pre>
</li>
--- 2024,2028 ----
<p>If the command line client executable is found the macro<br><pre> Subversion_WC_INFO(<dir> <var-prefix>)<br></pre>
<p>is defined to extract information of a subversion working copy at a given location. The macro defines the following variables:<br><pre> <var-prefix>_WC_URL - url of the repository (at <dir>)<br> <var-prefix>_WC_ROOT - root url of the repository<br> <var-prefix>_WC_REVISION - current revision<br> <var-prefix>_WC_LAST_CHANGED_AUTHOR - author of last commit<br> <var-prefix>_WC_LAST_CHANGED_DATE - date of last commit<br> <var-prefix>_WC_LAST_CHANGED_REV - revision of last commit<br> <var-prefix>_WC_LAST_CHANGED_LOG - last log of base revision<br> <var-prefix>_WC_INFO - output of command `svn info <dir>'<br></pre>
! <p>Example usage:<br><pre> FIND_PACKAGE(Subversion)<br> IF(Subversion_FOUND)<br> Subversion_WC_INFO(${PROJECT_SOURCE_DIR} Project)<br> MESSAGE("Current revision is ${Project_WC_REVISION}")<br> Subversion_WC_LOG(${PROJECT_SOURCE_DIR} Project)<br> MESSAGE("Last changed log is ${Project_LAST_CHANGED_LOG}")<br> ENDIF(Subversion_FOUND)<br></pre>
</li>
***************
*** 2110,2114 ****
<h2><a name="section_Policies"/>Policies</h2>
<ul>
! <li><a href="#policy:CMP0000"><b><code>CMP0000</code></b></a></li> <li><a href="#policy:CMP0001"><b><code>CMP0001</code></b></a></li> <li><a href="#policy:CMP0002"><b><code>CMP0002</code></b></a></li> <li><a href="#policy:CMP0003"><b><code>CMP0003</code></b></a></li> <li><a href="#policy:CMP0004"><b><code>CMP0004</code></b></a></li> <li><a href="#policy:CMP0005"><b><code>CMP0005</code></b></a></li> <li><a href="#policy:CMP0006"><b><code>CMP0006</code></b></a></li> <li><a href="#policy:CMP0007"><b><code>CMP0007</code></b></a></li></ul>
<ul>
<li>
--- 2254,2258 ----
<h2><a name="section_Policies"/>Policies</h2>
<ul>
! <li><a href="#policy:CMP0000"><b><code>CMP0000</code></b></a></li> <li><a href="#policy:CMP0001"><b><code>CMP0001</code></b></a></li> <li><a href="#policy:CMP0002"><b><code>CMP0002</code></b></a></li> <li><a href="#policy:CMP0003"><b><code>CMP0003</code></b></a></li> <li><a href="#policy:CMP0004"><b><code>CMP0004</code></b></a></li> <li><a href="#policy:CMP0005"><b><code>CMP0005</code></b></a></li> <li><a href="#policy:CMP0006"><b><code>CMP0006</code></b></a></li> <li><a href="#policy:CMP0007"><b><code>CMP0007</code></b></a></li> <li><a href="#policy:CMP0008"><b><code>CMP0008</code></b></a></li></ul>
<ul>
<li>
***************
*** 2156,2159 ****
--- 2300,2308 ----
<p>This policy determines whether the list command will ignore empty elements in the list. CMake 2.4 and below list commands ignored all empty elements in the list. For example, a;b;;c would have length 3 and not 4. The OLD behavior for this policy is to ignore empty list elements. The NEW behavior for this policy is to correctly count empty elements in a list. <br><p>This policy was introduced in CMake version 2.6.0. CMake version 2.6 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.
</li>
+ <li>
+ <a name="policy:CMP0008"><b><code>CMP0008</code></b></a>: Libraries linked by full-path must have a valid library file name.<br>
+ <p>In CMake 2.4 and below it is possible to write code like<br><pre> target_link_libraries(myexe /full/path/to/somelib)<br></pre>
+ <p>where "somelib" is supposed to be a valid library file name such as "libsomelib.a" or "somelib.lib". For Makefile generators this produces an error at build time because the dependency on the full path cannot be found. For VS IDE and Xcode generators this used to work by accident because CMake would always split off the library directory and ask the linker to search for the library by name (-lsomelib or somelib.lib). Despite the failure with Makefiles, some projects have code like this and build only with VS and/or Xcode. This version of CMake prefers to pass the full path directly to the native build tool, which will fail in this case because it does not name a valid library file.<br><p>This policy determines what to do with full paths that do not appear to name a valid library file. The OLD behavior for this policy is to split the library name from the path and ask the linker to search for it. The NEW behavior for this policy is to trust the given path and pass it directly to the native build tool unchanged.<br><p>This policy was introduced in CMake version 2.6.1. CMake version 2.6 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.
+ </li>
</ul>
<h2><a name="section_Variables"/>Variables</h2>
***************
*** 2162,2166 ****
<h2><a name="section_Variables That Change Behavior"/>Variables That Change Behavior</h2>
<ul>
! <li><a href="#variable:BUILD_SHARED_LIBS"><b><code>BUILD_SHARED_LIBS</code></b></a></li> <li><a href="#variable:CMAKE_BACKWARDS_COMPATIBILITY"><b><code>CMAKE_BACKWARDS_COMPATIBILITY</code></b></a></li> <li><a href="#variable:CMAKE_BUILD_TYPE"><b><code>CMAKE_BUILD_TYPE</code></b></a></li> <li><a href="#variable:CMAKE_CONFIGURATION_TYPES"><b><code>CMAKE_CONFIGURATION_TYPES</code></b></a></li> <li><a href="#variable:CMAKE_CROSSCOMPILING"><b><code>CMAKE_CROSSCOMPILING</code></b></a></li> <li><a href="#variable:CMAKE_FIND_LIBRARY_PREFIXES"><b><code>CMAKE_FIND_LIBRARY_PREFIXES</code></b></a></li> <li><a href="#variable:CMAKE_FIND_LIBRARY_SUFFIXES"><b><code>CMAKE_FIND_LIBRARY_SUFFIXES</code></b></a></li> <li><a href="#variable:CMAKE_INSTALL_PREFIX"><b><code>CMAKE_INSTALL_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_MFC_FLAG"><b><code>CMAKE_MFC_FLAG</code></b></a></li> <li><a href="#variable:CMAKE_MODULE_PATH"><b><code>CMAKE_MODULE_PATH</code></b></a></li> <li><a href="#variable:CMAKE_NOT_USING_CONFIG_FLAGS"><b><code>CMAKE_NOT_USING_CONFIG_FLAGS</code></b></a></li> <li><a href="#variable:CMAKE_USER_MAKE_RULES_OVERRIDE"><b><code>CMAKE_USER_MAKE_RULES_OVERRIDE</code></b></a></li></ul>
<ul>
<li>
--- 2311,2315 ----
<h2><a name="section_Variables That Change Behavior"/>Variables That Change Behavior</h2>
<ul>
! <li><a href="#variable:BUILD_SHARED_LIBS"><b><code>BUILD_SHARED_LIBS</code></b></a></li> <li><a href="#variable:CMAKE_BACKWARDS_COMPATIBILITY"><b><code>CMAKE_BACKWARDS_COMPATIBILITY</code></b></a></li> <li><a href="#variable:CMAKE_BUILD_TYPE"><b><code>CMAKE_BUILD_TYPE</code></b></a></li> <li><a href="#variable:CMAKE_CONFIGURATION_TYPES"><b><code>CMAKE_CONFIGURATION_TYPES</code></b></a></li> <li><a href="#variable:CMAKE_FIND_LIBRARY_PREFIXES"><b><code>CMAKE_FIND_LIBRARY_PREFIXES</code></b></a></li> <li><a href="#variable:CMAKE_FIND_LIBRARY_SUFFIXES"><b><code>CMAKE_FIND_LIBRARY_SUFFIXES</code></b></a></li> <li><a href="#variable:CMAKE_INCLUDE_PATH"><b><code>CMAKE_INCLUDE_PATH</code></b></a></li> <li><a href="#variable:CMAKE_INSTALL_PREFIX"><b><code>CMAKE_INSTALL_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_LIBRARY_PATH"><b><code>CMAKE_LIBRARY_PATH</code></b></a></li> <li><a href="#variable:CMAKE_MFC_FLAG"><b><code>CMAKE_MFC_FLAG</code></b></a></li> <li><a href="#variable:CMAKE_MODULE_PATH"><b><code>CMAKE_MODULE_PATH</code></b></a></li> <li><a href="#variable:CMAKE_NOT_USING_CONFIG_FLAGS"><b><code>CMAKE_NOT_USING_CONFIG_FLAGS</code></b></a></li> <li><a href="#variable:CMAKE_PREFIX_PATH"><b><code>CMAKE_PREFIX_PATH</code></b></a></li> <li><a href="#variable:CMAKE_PROGRAM_PATH"><b><code>CMAKE_PROGRAM_PATH</code></b></a></li> <li><a href="#variable:CMAKE_SYSTEM_INCLUDE_PATH"><b><code>CMAKE_SYSTEM_INCLUDE_PATH</code></b></a></li> <li><a href="#variable:CMAKE_SYSTEM_LIBRARY_PATH"><b><code>CMAKE_SYSTEM_LIBRARY_PATH</code></b></a></li> <li><a href="#variable:CMAKE_SYSTEM_PREFIX_PATH"><b><code>CMAKE_SYSTEM_PREFIX_PATH</code></b></a></li> <li><a href="#variable:CMAKE_SYSTEM_PROGRAM_PATH"><b><code>CMAKE_SYSTEM_PROGRAM_PATH</code></b></a></li> <li><a href="#variable:CMAKE_USER_MAKE_RULES_OVERRIDE"><b><code>CMAKE_USER_MAKE_RULES_OVERRIDE</code></b></a></li></ul>
<ul>
<li>
***************
*** 2181,2188 ****
</li>
<li>
- <a name="variable:CMAKE_CROSSCOMPILING"><b><code>CMAKE_CROSSCOMPILING</code></b></a>: Is CMake currently cross compiling.<br>
- <p>This variable will be set to true by CMake if CMake is cross compiling. Specifically if the build platform is different from the target platform.
- </li>
- <li>
<a name="variable:CMAKE_FIND_LIBRARY_PREFIXES"><b><code>CMAKE_FIND_LIBRARY_PREFIXES</code></b></a>: Prefixes to prepend when looking for libraries.<br>
<p>This specifies what prefixes to add to library names when the find_library command looks for libraries. On UNIX systems this is typically lib, meaning that when trying to find the foo library it will look for libfoo.
--- 2330,2333 ----
***************
*** 2193,2200 ****
--- 2338,2353 ----
</li>
<li>
+ <a name="variable:CMAKE_INCLUDE_PATH"><b><code>CMAKE_INCLUDE_PATH</code></b></a>: Path used for searching by FIND_FILE() and FIND_PATH().<br>
+ <p>Specifies a path which will be used both by FIND_FILE() and FIND_PATH(). Both commands will check each of the contained directories for the existence of the file which is currently searched. By default it is empty, it is intended to be set by the project. See also CMAKE_SYSTEM_INCLUDE_PATH, CMAKE_PREFIX_PATH.
+ </li>
+ <li>
<a name="variable:CMAKE_INSTALL_PREFIX"><b><code>CMAKE_INSTALL_PREFIX</code></b></a>: Install directory used by install.<br>
<p>If "make install" is invoked or INSTALL is built, this directory is pre-pended onto all install directories. This variable defaults to /usr/local on UNIX and c:/Program Files on Windows.
</li>
<li>
+ <a name="variable:CMAKE_LIBRARY_PATH"><b><code>CMAKE_LIBRARY_PATH</code></b></a>: Path used for searching by FIND_LIBRARY().<br>
+ <p>Specifies a path which will be used by FIND_LIBRARY(). FIND_LIBRARY() will check each of the contained directories for the existence of the library which is currently searched. By default it is empty, it is intended to be set by the project. See also CMAKE_SYSTEM_LIBRARY_PATH, CMAKE_PREFIX_PATH.
+ </li>
+ <li>
<a name="variable:CMAKE_MFC_FLAG"><b><code>CMAKE_MFC_FLAG</code></b></a>: Tell cmake to use MFC for an executable or dll.<br>
<p>This can be set in a CMakeLists.txt file and will enable MFC in the application. It should be set to 1 for static the static MFC library, and 2 for the shared MFC library. This is used in visual studio 6 and 7 project files. The CMakeSetup dialog uses MFC and the CMakeLists.txt looks like this:<br><p>ADD_DEFINITIONS(-D_AFXDLL)<br><p>set(CMAKE_MFC_FLAG 2)<br><p>add_executable(CMakeSetup WIN32 ${SRCS})<br>
***************
*** 2209,2212 ****
--- 2362,2389 ----
</li>
<li>
+ <a name="variable:CMAKE_PREFIX_PATH"><b><code>CMAKE_PREFIX_PATH</code></b></a>: Path used for searching by FIND_XXX(), with appropriate suffixes added.<br>
+ <p>Specifies a path which will be used by the FIND_XXX() commands. It contains the "base" directories, the FIND_XXX() commands append appropriate subdirectories to the base directories. So FIND_PROGRAM() adds /bin to each of the directories in the path, FIND_LIBRARY() appends /lib to each of the directories, and FIND_PATH() and FIND_FILE() append /include . By default it is empty, it is intended to be set by the project. See also CMAKE_SYSTEM_PREFIX_PATH, CMAKE_INCLUDE_PATH, CMAKE_LIBRARY_PATH, CMAKE_PROGRAM_PATH.
+ </li>
+ <li>
+ <a name="variable:CMAKE_PROGRAM_PATH"><b><code>CMAKE_PROGRAM_PATH</code></b></a>: Path used for searching by FIND_PROGRAM().<br>
+ <p>Specifies a path which will be used by FIND_PROGRAM(). FIND_PROGRAM() will check each of the contained directories for the existence of the program which is currently searched. By default it is empty, it is intended to be set by the project. See also CMAKE_SYSTEM_PROGRAM_PATH, CMAKE_PREFIX_PATH.
+ </li>
+ <li>
+ <a name="variable:CMAKE_SYSTEM_INCLUDE_PATH"><b><code>CMAKE_SYSTEM_INCLUDE_PATH</code></b></a>: Path used for searching by FIND_FILE() and FIND_PATH().<br>
+ <p>Specifies a path which will be used both by FIND_FILE() and FIND_PATH(). Both commands will check each of the contained directories for the existence of the file which is currently searched. By default it contains the standard directories for the current system. It is NOT intended to be modified by the project, use CMAKE_INCLUDE_PATH for this. See also CMAKE_SYSTEM_PREFIX_PATH.
+ </li>
+ <li>
+ <a name="variable:CMAKE_SYSTEM_LIBRARY_PATH"><b><code>CMAKE_SYSTEM_LIBRARY_PATH</code></b></a>: Path used for searching by FIND_LIBRARY().<br>
+ <p>Specifies a path which will be used by FIND_LIBRARY(). FIND_LIBRARY() will check each of the contained directories for the existence of the library which is currently searched. By default it contains the standard directories for the current system. It is NOT intended to be modified by the project, use CMAKE_SYSTEM_LIBRARY_PATH for this. See also CMAKE_SYSTEM_PREFIX_PATH.
+ </li>
+ <li>
+ <a name="variable:CMAKE_SYSTEM_PREFIX_PATH"><b><code>CMAKE_SYSTEM_PREFIX_PATH</code></b></a>: Path used for searching by FIND_XXX(), with appropriate suffixes added.<br>
+ <p>Specifies a path which will be used by the FIND_XXX() commands. It contains the "base" directories, the FIND_XXX() commands append appropriate subdirectories to the base directories. So FIND_PROGRAM() adds /bin to each of the directories in the path, FIND_LIBRARY() appends /lib to each of the directories, and FIND_PATH() and FIND_FILE() append /include . By default this contains the standard directories for the current system. It is NOT intended to be modified by the project, use CMAKE_PREFIX_PATH for this. See also CMAKE_SYSTEM_INCLUDE_PATH, CMAKE_SYSTEM_LIBRARY_PATH, CMAKE_SYSTEM_PROGRAM_PATH.
+ </li>
+ <li>
+ <a name="variable:CMAKE_SYSTEM_PROGRAM_PATH"><b><code>CMAKE_SYSTEM_PROGRAM_PATH</code></b></a>: Path used for searching by FIND_PROGRAM().<br>
+ <p>Specifies a path which will be used by FIND_PROGRAM(). FIND_PROGRAM() will check each of the contained directories for the existence of the program which is currently searched. By default it contains the standard directories for the current system. It is NOT intended to be modified by the project, use CMAKE_PROGRAM_PATH for this. See also CMAKE_SYSTEM_PREFIX_PATH.
+ </li>
+ <li>
<a name="variable:CMAKE_USER_MAKE_RULES_OVERRIDE"><b><code>CMAKE_USER_MAKE_RULES_OVERRIDE</code></b></a>: Specify a file that can change the build rule variables.<br>
<p>If this variable is set, it should to point to a CMakeLists.txt file that will be read in by CMake after all the system settings have been set, but before they have been used. This would allow you to override any variables that need to be changed for some special project.
***************
*** 2490,2494 ****
<h2><a name="section_Variables that Provide Information"/>Variables that Provide Information</h2>
<ul>
! <li><a href="#variable:CMAKE_AR"><b><code>CMAKE_AR</code></b></a></li> <li><a href="#variable:CMAKE_BINARY_DIR"><b><code>CMAKE_BINARY_DIR</code></b></a></li> <li><a href="#variable:CMAKE_BUILD_TOOL"><b><code>CMAKE_BUILD_TOOL</code></b></a></li> <li><a href="#variable:CMAKE_CACHEFILE_DIR"><b><code>CMAKE_CACHEFILE_DIR</code></b></a></li> <li><a href="#variable:CMAKE_CACHE_MAJOR_VERSION"><b><code>CMAKE_CACHE_MAJOR_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_CACHE_MINOR_VERSION"><b><code>CMAKE_CACHE_MINOR_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_CACHE_RELEASE_VERSION"><b><code>CMAKE_CACHE_RELEASE_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_CFG_INTDIR"><b><code>CMAKE_CFG_INTDIR</code></b></a></li> <li><a href="#variable:CMAKE_COMMAND"><b><code>CMAKE_COMMAND</code></b></a></li> <li><a href="#variable:CMAKE_CTEST_COMMAND"><b><code>CMAKE_CTEST_COMMAND</code></b></a></li> <li><a href="#variable:CMAKE_CURRENT_BINARY_DIR"><b><code>CMAKE_CURRENT_BINARY_DIR</code></b></a></li> <li><a href="#variable:CMAKE_CURRENT_LIST_FILE"><b><code>CMAKE_CURRENT_LIST_FILE</code></b></a></li> <li><a href="#variable:CMAKE_CURRENT_LIST_LINE"><b><code>CMAKE_CURRENT_LIST_LINE</code></b></a></li> <li><a href="#variable:CMAKE_CURRENT_SOURCE_DIR"><b><code>CMAKE_CURRENT_SOURCE_DIR</code></b></a></li> <li><a href="#variable:CMAKE_DL_LIBS"><b><code>CMAKE_DL_LIBS</code></b></a></li> <li><a href="#variable:CMAKE_EDIT_COMMAND"><b><code>CMAKE_EDIT_COMMAND</code></b></a></li> <li><a href="#variable:CMAKE_EXECUTABLE_SUFFIX"><b><code>CMAKE_EXECUTABLE_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_GENERATOR"><b><code>CMAKE_GENERATOR</code></b></a></li> <li><a href="#variable:CMAKE_HOME_DIRECTORY"><b><code>CMAKE_HOME_DIRECTORY</code></b></a></li> <li><a href="#variable:CMAKE_IMPORT_LIBRARY_PREFIX"><b><code>CMAKE_IMPORT_LIBRARY_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_IMPORT_LIBRARY_SUFFIX"><b><code>CMAKE_IMPORT_LIBRARY_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_LINK_LIBRARY_SUFFIX"><b><code>CMAKE_LINK_LIBRARY_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_MAJOR_VERSION"><b><code>CMAKE_MAJOR_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_MAKE_PROGRAM"><b><code>CMAKE_MAKE_PROGRAM</code></b></a></li> <li><a href="#variable:CMAKE_MINOR_VERSION"><b><code>CMAKE_MINOR_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_PARENT_LIST_FILE"><b><code>CMAKE_PARENT_LIST_FILE</code></b></a></li> <li><a href="#variable:CMAKE_PROJECT_NAME"><b><code>CMAKE_PROJECT_NAME</code></b></a></li> <li><a href="#variable:CMAKE_RANLIB"><b><code>CMAKE_RANLIB</code></b></a></li> <li><a href="#variable:CMAKE_ROOT"><b><code>CMAKE_ROOT</code></b></a></li> <li><a href="#variable:CMAKE_SHARED_LIBRARY_PREFIX"><b><code>CMAKE_SHARED_LIBRARY_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_SHARED_LIBRARY_SUFFIX"><b><code>CMAKE_SHARED_LIBRARY_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_SHARED_MODULE_PREFIX"><b><code>CMAKE_SHARED_MODULE_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_SHARED_MODULE_SUFFIX"><b><code>CMAKE_SHARED_MODULE_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_SIZEOF_VOID_P"><b><code>CMAKE_SIZEOF_VOID_P</code></b></a></li> <li><a href="#variable:CMAKE_SKIP_RPATH"><b><code>CMAKE_SKIP_RPATH</code></b></a></li> <li><a href="#variable:CMAKE_SOURCE_DIR"><b><code>CMAKE_SOURCE_DIR</code></b></a></li> <li><a href="#variable:CMAKE_STANDARD_LIBRARIES"><b><code>CMAKE_STANDARD_LIBRARIES</code></b></a></li> <li><a href="#variable:CMAKE_STATIC_LIBRARY_PREFIX"><b><code>CMAKE_STATIC_LIBRARY_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_STATIC_LIBRARY_SUFFIX"><b><code>CMAKE_STATIC_LIBRARY_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_USING_VC_FREE_TOOLS"><b><code>CMAKE_USING_VC_FREE_TOOLS</code></b></a></li> <li><a href="#variable:CMAKE_VERBOSE_MAKEFILE"><b><code>CMAKE_VERBOSE_MAKEFILE</code></b></a></li> <li><a href="#variable:PROJECT_BINARY_DIR"><b><code>PROJECT_BINARY_DIR</code></b></a></li> <li><a href="#variable:PROJECT_NAME"><b><code>PROJECT_NAME</code></b></a></li> <li><a href="#variable:PROJECT_SOURCE_DIR"><b><code>PROJECT_SOURCE_DIR</code></b></a></li> <li><a href="#variable:Projectname_BINARY_DIR"><b><code>[Project name]_BINARY_DIR</code></b></a></li> <li><a href="#variable:Projectname_SOURCE_DIR"><b><code>[Project name]_SOURCE_DIR</code></b></a></li></ul>
<p>variables defined by cmake, that give information about the project, and cmake
<ul>
--- 2667,2671 ----
<h2><a name="section_Variables that Provide Information"/>Variables that Provide Information</h2>
<ul>
! <li><a href="#variable:CMAKE_AR"><b><code>CMAKE_AR</code></b></a></li> <li><a href="#variable:CMAKE_BINARY_DIR"><b><code>CMAKE_BINARY_DIR</code></b></a></li> <li><a href="#variable:CMAKE_BUILD_TOOL"><b><code>CMAKE_BUILD_TOOL</code></b></a></li> <li><a href="#variable:CMAKE_CACHEFILE_DIR"><b><code>CMAKE_CACHEFILE_DIR</code></b></a></li> <li><a href="#variable:CMAKE_CACHE_MAJOR_VERSION"><b><code>CMAKE_CACHE_MAJOR_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_CACHE_MINOR_VERSION"><b><code>CMAKE_CACHE_MINOR_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_CACHE_RELEASE_VERSION"><b><code>CMAKE_CACHE_RELEASE_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_CFG_INTDIR"><b><code>CMAKE_CFG_INTDIR</code></b></a></li> <li><a href="#variable:CMAKE_COMMAND"><b><code>CMAKE_COMMAND</code></b></a></li> <li><a href="#variable:CMAKE_CROSSCOMPILING"><b><code>CMAKE_CROSSCOMPILING</code></b></a></li> <li><a href="#variable:CMAKE_CTEST_COMMAND"><b><code>CMAKE_CTEST_COMMAND</code></b></a></li> <li><a href="#variable:CMAKE_CURRENT_BINARY_DIR"><b><code>CMAKE_CURRENT_BINARY_DIR</code></b></a></li> <li><a href="#variable:CMAKE_CURRENT_LIST_FILE"><b><code>CMAKE_CURRENT_LIST_FILE</code></b></a></li> <li><a href="#variable:CMAKE_CURRENT_LIST_LINE"><b><code>CMAKE_CURRENT_LIST_LINE</code></b></a></li> <li><a href="#variable:CMAKE_CURRENT_SOURCE_DIR"><b><code>CMAKE_CURRENT_SOURCE_DIR</code></b></a></li> <li><a href="#variable:CMAKE_DL_LIBS"><b><code>CMAKE_DL_LIBS</code></b></a></li> <li><a href="#variable:CMAKE_EDIT_COMMAND"><b><code>CMAKE_EDIT_COMMAND</code></b></a></li> <li><a href="#variable:CMAKE_EXECUTABLE_SUFFIX"><b><code>CMAKE_EXECUTABLE_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_GENERATOR"><b><code>CMAKE_GENERATOR</code></b></a></li> <li><a href="#variable:CMAKE_HOME_DIRECTORY"><b><code>CMAKE_HOME_DIRECTORY</code></b></a></li> <li><a href="#variable:CMAKE_IMPORT_LIBRARY_PREFIX"><b><code>CMAKE_IMPORT_LIBRARY_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_IMPORT_LIBRARY_SUFFIX"><b><code>CMAKE_IMPORT_LIBRARY_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_LINK_LIBRARY_SUFFIX"><b><code>CMAKE_LINK_LIBRARY_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_MAJOR_VERSION"><b><code>CMAKE_MAJOR_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_MAKE_PROGRAM"><b><code>CMAKE_MAKE_PROGRAM</code></b></a></li> <li><a href="#variable:CMAKE_MINOR_VERSION"><b><code>CMAKE_MINOR_VERSION</code></b></a></li> <li><a href="#variable:CMAKE_PARENT_LIST_FILE"><b><code>CMAKE_PARENT_LIST_FILE</code></b></a></li> <li><a href="#variable:CMAKE_PROJECT_NAME"><b><code>CMAKE_PROJECT_NAME</code></b></a></li> <li><a href="#variable:CMAKE_RANLIB"><b><code>CMAKE_RANLIB</code></b></a></li> <li><a href="#variable:CMAKE_ROOT"><b><code>CMAKE_ROOT</code></b></a></li> <li><a href="#variable:CMAKE_SHARED_LIBRARY_PREFIX"><b><code>CMAKE_SHARED_LIBRARY_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_SHARED_LIBRARY_SUFFIX"><b><code>CMAKE_SHARED_LIBRARY_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_SHARED_MODULE_PREFIX"><b><code>CMAKE_SHARED_MODULE_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_SHARED_MODULE_SUFFIX"><b><code>CMAKE_SHARED_MODULE_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_SIZEOF_VOID_P"><b><code>CMAKE_SIZEOF_VOID_P</code></b></a></li> <li><a href="#variable:CMAKE_SKIP_RPATH"><b><code>CMAKE_SKIP_RPATH</code></b></a></li> <li><a href="#variable:CMAKE_SOURCE_DIR"><b><code>CMAKE_SOURCE_DIR</code></b></a></li> <li><a href="#variable:CMAKE_STANDARD_LIBRARIES"><b><code>CMAKE_STANDARD_LIBRARIES</code></b></a></li> <li><a href="#variable:CMAKE_STATIC_LIBRARY_PREFIX"><b><code>CMAKE_STATIC_LIBRARY_PREFIX</code></b></a></li> <li><a href="#variable:CMAKE_STATIC_LIBRARY_SUFFIX"><b><code>CMAKE_STATIC_LIBRARY_SUFFIX</code></b></a></li> <li><a href="#variable:CMAKE_USING_VC_FREE_TOOLS"><b><code>CMAKE_USING_VC_FREE_TOOLS</code></b></a></li> <li><a href="#variable:CMAKE_VERBOSE_MAKEFILE"><b><code>CMAKE_VERBOSE_MAKEFILE</code></b></a></li> <li><a href="#variable:PROJECT_BINARY_DIR"><b><code>PROJECT_BINARY_DIR</code></b></a></li> <li><a href="#variable:PROJECT_NAME"><b><code>PROJECT_NAME</code></b></a></li> <li><a href="#variable:PROJECT_SOURCE_DIR"><b><code>PROJECT_SOURCE_DIR</code></b></a></li> <li><a href="#variable:Projectname_BINARY_DIR"><b><code>[Project name]_BINARY_DIR</code></b></a></li> <li><a href="#variable:Projectname_SOURCE_DIR"><b><code>[Project name]_SOURCE_DIR</code></b></a></li></ul>
<p>variables defined by cmake, that give information about the project, and cmake
<ul>
***************
*** 2530,2533 ****
--- 2707,2714 ----
</li>
<li>
+ <a name="variable:CMAKE_CROSSCOMPILING"><b><code>CMAKE_CROSSCOMPILING</code></b></a>: Is CMake currently cross compiling.<br>
+ <p>This variable will be set to true by CMake if CMake is cross compiling. Specifically if the build platform is different from the target platform.
+ </li>
+ <li>
<a name="variable:CMAKE_CTEST_COMMAND"><b><code>CMAKE_CTEST_COMMAND</code></b></a>: Full path to ctest command installed with cmake.<br>
<p>This is the full path to the CTest executable ctest which is useful from custom commands that want to use the cmake -E option for portable system commands.
Index: Download.html
===================================================================
RCS file: /cvsroot/CMake/CMakeWeb/HTML/Download.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -C 2 -d -r1.6 -r1.7
*** Download.html 6 May 2008 18:16:17 -0000 1.6
--- Download.html 1 Aug 2008 16:50:29 -0000 1.7
***************
*** 88,99 ****
distribution through CVS. You can also download high-resolution <a href="#logos">logos</a>.</p>
! <a name="latest"><h3>Latest Release (2.6.0)</h3></a>
! <p>The 2.6.0 release was packaged with CPack which is included as part of the 2.6.0 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 SunOS-sparc tar file is all
! under the directory cmake-2.6.0-SunOS-sparc. This prefix can be removed as long as the share, bin, man and doc
directories are moved relative to each other.</p>
<p>To build the source distributions, unpack them with zip or tar and follow the instructions in Readme.txt at
--- 88,99 ----
distribution through CVS. You can also download high-resolution <a href="#logos">logos</a>.</p>
! <a name="latest"><h3>Latest Release (2.6.1)</h3></a>
! <p>The 2.6.1 release was packaged with CPack which is included as part of the 2.6.1 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 SunOS-sparc tar file is all
! under the directory cmake-2.6.1-SunOS-sparc. This prefix can be removed as long as the share, bin, man and doc
directories are moved relative to each other.</p>
<p>To build the source distributions, unpack them with zip or tar and follow the instructions in Readme.txt at
***************
*** 105,112 ****
<table bgcolor="#ffffff" border="0" cellspacing="0" width="100%">
<tbody><tr class="table-heading" bgcolor="#e0e0e0"><td><b>Platform</b></td><td><b>Files</b></td></tr>
! <tr bgcolor="#f0f0f0"><td>Unix/Linux Source (has \n line feeds)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0.tar.gz">cmake-2.6.0.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0.tar.Z">cmake-2.6.0.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>Windows Source (has \r\n line feeds)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0.zip">cmake-2.6.0.zip</a></td></tr>
</tbody></table>
</td></tr></tbody></table>
--- 105,112 ----
<table bgcolor="#ffffff" border="0" cellspacing="0" width="100%">
<tbody><tr class="table-heading" bgcolor="#e0e0e0"><td><b>Platform</b></td><td><b>Files</b></td></tr>
! <tr bgcolor="#f0f0f0"><td>Unix/Linux Source (has \n line feeds)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1.tar.gz">cmake-2.6.1.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1.tar.Z">cmake-2.6.1.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>Windows Source (has \r\n line feeds)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1.zip">cmake-2.6.1.zip</a></td></tr>
</tbody></table>
</td></tr></tbody></table>
***************
*** 118,154 ****
<tbody><tr class="table-heading" bgcolor="#e0e0e0"><td><b>Platform</b></td><td><b>Files</b></td></tr>
! <tr bgcolor="#f0f0f0"><td>Windows (Win32 Installer)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-win32-x86.exe">cmake-2.6.0-win32-x86.exe</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>Windows ZIP</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-win32-x86.zip">cmake-2.6.0-win32-x86.zip</a></td></tr>
! <tr bgcolor="#ffffff"><td>Mac OSX Universal (.dmg installer only for Tiger)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Darwin-universal.dmg">cmake-2.6.0-Darwin-universal.dmg</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Darwin-universal.tar.gz">cmake-2.6.0-Darwin-universal.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Darwin-universal.tar.Z">cmake-2.6.0-Darwin-universal.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>Linux i386</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Linux-i386.sh">cmake-2.6.0-Linux-i386.sh</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Linux-i386.tar.gz">cmake-2.6.0-Linux-i386.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Linux-i386.tar.Z">cmake-2.6.0-Linux-i386.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>SunOS Sparc</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-SunOS-sparc.sh">cmake-2.6.0-SunOS-sparc.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-SunOS-sparc.tar.gz">cmake-2.6.0-SunOS-sparc.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-SunOS-sparc.tar.Z">cmake-2.6.0-SunOS-sparc.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>IRIX64 64</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-64.sh">cmake-2.6.0-IRIX64-64.sh </a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-64.tar.gz">cmake-2.6.0-IRIX64-64.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-64.tar.Z">cmake-2.6.0-IRIX64-64.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>IRIX64 n32</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-n32.sh">cmake-2.6.0-IRIX64-n32.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-n32.tar.gz">cmake-2.6.0-IRIX64-n32.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-n32.tar.Z">cmake-2.6.0-IRIX64-n32.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>HPUX 9000/785</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-HP-UX-9000_785.sh">cmake-2.6.0-HP-UX-9000_785.sh</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-HP-UX-9000_785.tar.gz">cmake-2.6.0-HP-UX-9000_785.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-HP-UX-9000_785.tar.Z">cmake-2.6.0-HP-UX-9000_785.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>AIX powerpc</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-AIX-powerpc.sh">cmake-2.6.0-AIX-powerpc.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-AIX-powerpc.tar.Z">cmake-2.6.0-AIX-powerpc.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-AIX-powerpc.tar.gz">cmake-2.6.0-AIX-powerpc.tar.gz</a></td></tr>
--- 118,154 ----
<tbody><tr class="table-heading" bgcolor="#e0e0e0"><td><b>Platform</b></td><td><b>Files</b></td></tr>
! <tr bgcolor="#f0f0f0"><td>Windows (Win32 Installer)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-win32-x86.exe">cmake-2.6.1-win32-x86.exe</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>Windows ZIP</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-win32-x86.zip">cmake-2.6.1-win32-x86.zip</a></td></tr>
! <tr bgcolor="#ffffff"><td>Mac OSX Universal (.dmg installer only for Tiger)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Darwin-universal.dmg">cmake-2.6.1-Darwin-universal.dmg</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Darwin-universal.tar.gz">cmake-2.6.1-Darwin-universal.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Darwin-universal.tar.Z">cmake-2.6.1-Darwin-universal.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>Linux i386</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Linux-i386.sh">cmake-2.6.1-Linux-i386.sh</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Linux-i386.tar.gz">cmake-2.6.1-Linux-i386.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Linux-i386.tar.Z">cmake-2.6.1-Linux-i386.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>SunOS Sparc</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-SunOS-sparc.sh">cmake-2.6.1-SunOS-sparc.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-SunOS-sparc.tar.gz">cmake-2.6.1-SunOS-sparc.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-SunOS-sparc.tar.Z">cmake-2.6.1-SunOS-sparc.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>IRIX64 64</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-64.sh">cmake-2.6.1-IRIX64-64.sh </a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-64.tar.gz">cmake-2.6.1-IRIX64-64.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-64.tar.Z">cmake-2.6.1-IRIX64-64.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>IRIX64 n32</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-n32.sh">cmake-2.6.1-IRIX64-n32.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-n32.tar.gz">cmake-2.6.1-IRIX64-n32.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-n32.tar.Z">cmake-2.6.1-IRIX64-n32.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>HPUX 9000/785</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-HP-UX-9000_785.sh">cmake-2.6.1-HP-UX-9000_785.sh</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-HP-UX-9000_785.tar.gz">cmake-2.6.1-HP-UX-9000_785.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-HP-UX-9000_785.tar.Z">cmake-2.6.1-HP-UX-9000_785.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>AIX powerpc</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-AIX-powerpc.sh">cmake-2.6.1-AIX-powerpc.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-AIX-powerpc.tar.Z">cmake-2.6.1-AIX-powerpc.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-AIX-powerpc.tar.gz">cmake-2.6.1-AIX-powerpc.tar.gz</a></td></tr>
Index: index.html
===================================================================
RCS file: /cvsroot/CMake/CMakeWeb/HTML/index.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -C 2 -d -r1.15 -r1.16
*** index.html 6 May 2008 18:16:17 -0000 1.15
--- index.html 1 Aug 2008 16:50:29 -0000 1.16
***************
*** 140,151 ****
</div>
<div class="TabbedPanelsContent">
! <p><strong>Latest Release (2.6.0)</strong></p>
<ul>
! <li>The 2.6.0 release was packaged with CPack which is included as part of the 2.6.0 release.</li>
<li>The .sh files are self extracting gziped tar files. To install a .sh file, run it with /bin/sh and follow the directions.</li>
<li>The OS-machine.tar.gz files are gziped tar files of the install tree.</li>
<li>The OS-machine.tar.Z files are compressed tar files of the install tree.</li>
<li>The tar file distributions can be untared in any directory. They are prefixed by the version of CMake.
! For example, the SunOS-sparc tar file is all under the directory cmake-2.6.0-SunOS-sparc.
This prefix can be removed as long as the share, bin, man and doc directories are moved relative to each other.</li>
<li>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
--- 140,151 ----
</div>
<div class="TabbedPanelsContent">
! <p><strong>Latest Release (2.6.1)</strong></p>
<ul>
! <li>The 2.6.1 release was packaged with CPack which is included as part of the 2.6.1 release.</li>
<li>The .sh files are self extracting gziped tar files. To install a .sh file, run it with /bin/sh and follow the directions.</li>
<li>The OS-machine.tar.gz files are gziped tar files of the install tree.</li>
<li>The OS-machine.tar.Z files are compressed tar files of the install tree.</li>
<li>The tar file distributions can be untared in any directory. They are prefixed by the version of CMake.
! For example, the SunOS-sparc tar file is all under the directory cmake-2.6.1-SunOS-sparc.
This prefix can be removed as long as the share, bin, man and doc directories are moved relative to each other.</li>
<li>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
***************
*** 156,163 ****
<table bgcolor="#ffffff" border="0" cellspacing="0" width="100%">
<tbody><tr class="table-heading" bgcolor="#e0e0e0"><td><b>Platform</b></td><td><b>Files</b></td></tr>
! <tr bgcolor="#f0f0f0"><td>Unix/Linux Source (has \n line feeds)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0.tar.gz">cmake-2.6.0.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0.tar.Z">cmake-2.6.0.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>Windows Source (has \r\n line feeds)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0.zip">cmake-2.6.0.zip</a></td></tr>
</tbody></table>
</td></tr></tbody></table>
--- 156,163 ----
<table bgcolor="#ffffff" border="0" cellspacing="0" width="100%">
<tbody><tr class="table-heading" bgcolor="#e0e0e0"><td><b>Platform</b></td><td><b>Files</b></td></tr>
! <tr bgcolor="#f0f0f0"><td>Unix/Linux Source (has \n line feeds)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1.tar.gz">cmake-2.6.1.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1.tar.Z">cmake-2.6.1.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>Windows Source (has \r\n line feeds)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1.zip">cmake-2.6.1.zip</a></td></tr>
</tbody></table>
</td></tr></tbody></table>
***************
*** 169,205 ****
<tbody><tr class="table-heading" bgcolor="#e0e0e0"><td><b>Platform</b></td><td><b>Files</b></td></tr>
! <tr bgcolor="#f0f0f0"><td>Windows (Win32 Installer)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-win32-x86.exe">cmake-2.6.0-win32-x86.exe</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>Windows ZIP</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-win32-x86.zip">cmake-2.6.0-win32-x86.zip</a></td></tr>
! <tr bgcolor="#ffffff"><td>Mac OSX Universal (.dmg installer only for Tiger)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Darwin-universal.dmg">cmake-2.6.0-Darwin-universal.dmg</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Darwin-universal.tar.gz">cmake-2.6.0-Darwin-universal.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Darwin-universal.tar.Z">cmake-2.6.0-Darwin-universal.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>Linux i386</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Linux-i386.sh">cmake-2.6.0-Linux-i386.sh</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Linux-i386.tar.gz">cmake-2.6.0-Linux-i386.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-Linux-i386.tar.Z">cmake-2.6.0-Linux-i386.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>SunOS Sparc</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-SunOS-sparc.sh">cmake-2.6.0-SunOS-sparc.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-SunOS-sparc.tar.gz">cmake-2.6.0-SunOS-sparc.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-SunOS-sparc.tar.Z">cmake-2.6.0-SunOS-sparc.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>IRIX64 64</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-64.sh">cmake-2.6.0-IRIX64-64.sh </a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-64.tar.gz">cmake-2.6.0-IRIX64-64.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-64.tar.Z">cmake-2.6.0-IRIX64-64.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>IRIX64 n32</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-n32.sh">cmake-2.6.0-IRIX64-n32.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-n32.tar.gz">cmake-2.6.0-IRIX64-n32.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-IRIX64-n32.tar.Z">cmake-2.6.0-IRIX64-n32.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>HPUX 9000/785</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-HP-UX-9000_785.sh">cmake-2.6.0-HP-UX-9000_785.sh</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-HP-UX-9000_785.tar.gz">cmake-2.6.0-HP-UX-9000_785.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-HP-UX-9000_785.tar.Z">cmake-2.6.0-HP-UX-9000_785.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>AIX powerpc</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-AIX-powerpc.sh">cmake-2.6.0-AIX-powerpc.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-AIX-powerpc.tar.Z">cmake-2.6.0-AIX-powerpc.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.0-AIX-powerpc.tar.gz">cmake-2.6.0-AIX-powerpc.tar.gz</a></td></tr>
--- 169,205 ----
<tbody><tr class="table-heading" bgcolor="#e0e0e0"><td><b>Platform</b></td><td><b>Files</b></td></tr>
! <tr bgcolor="#f0f0f0"><td>Windows (Win32 Installer)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-win32-x86.exe">cmake-2.6.1-win32-x86.exe</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>Windows ZIP</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-win32-x86.zip">cmake-2.6.1-win32-x86.zip</a></td></tr>
! <tr bgcolor="#ffffff"><td>Mac OSX Universal (.dmg installer only for Tiger)</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Darwin-universal.dmg">cmake-2.6.1-Darwin-universal.dmg</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Darwin-universal.tar.gz">cmake-2.6.1-Darwin-universal.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Darwin-universal.tar.Z">cmake-2.6.1-Darwin-universal.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>Linux i386</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Linux-i386.sh">cmake-2.6.1-Linux-i386.sh</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Linux-i386.tar.gz">cmake-2.6.1-Linux-i386.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-Linux-i386.tar.Z">cmake-2.6.1-Linux-i386.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>SunOS Sparc</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-SunOS-sparc.sh">cmake-2.6.1-SunOS-sparc.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-SunOS-sparc.tar.gz">cmake-2.6.1-SunOS-sparc.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-SunOS-sparc.tar.Z">cmake-2.6.1-SunOS-sparc.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>IRIX64 64</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-64.sh">cmake-2.6.1-IRIX64-64.sh </a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-64.tar.gz">cmake-2.6.1-IRIX64-64.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-64.tar.Z">cmake-2.6.1-IRIX64-64.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>IRIX64 n32</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-n32.sh">cmake-2.6.1-IRIX64-n32.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-n32.tar.gz">cmake-2.6.1-IRIX64-n32.tar.gz</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-IRIX64-n32.tar.Z">cmake-2.6.1-IRIX64-n32.tar.Z</a></td></tr>
! <tr bgcolor="#f0f0f0"><td>HPUX 9000/785</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-HP-UX-9000_785.sh">cmake-2.6.1-HP-UX-9000_785.sh</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-HP-UX-9000_785.tar.gz">cmake-2.6.1-HP-UX-9000_785.tar.gz</a></td></tr>
! <tr bgcolor="#f0f0f0"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-HP-UX-9000_785.tar.Z">cmake-2.6.1-HP-UX-9000_785.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td>AIX powerpc</td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-AIX-powerpc.sh">cmake-2.6.1-AIX-powerpc.sh</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-AIX-powerpc.tar.Z">cmake-2.6.1-AIX-powerpc.tar.Z</a></td></tr>
! <tr bgcolor="#ffffff"><td></td><td><a href="http://www.cmake.org/files/v2.6/cmake-2.6.1-AIX-powerpc.tar.gz">cmake-2.6.1-AIX-powerpc.tar.gz</a></td></tr>
Index: ctest-2-6.html
===================================================================
RCS file: /cvsroot/CMake/CMakeWeb/HTML/ctest-2-6.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C 2 -d -r1.2 -r1.3
*** ctest-2-6.html 6 May 2008 14:50:35 -0000 1.2
--- ctest-2-6.html 1 Aug 2008 16:50:29 -0000 1.3
***************
*** 187,191 ****
<h2><a name="section_Commands"/>Commands</h2>
<ul>
! <li><a href="#command:break"><b><code>break</code></b></a></li> <li><a href="#command:build_name"><b><code>build_name</code></b></a></li> <li><a href="#command:cmake_minimum_required"><b><code>cmake_minimum_required</code></b></a></li> <li><a href="#command:cmake_policy"><b><code>cmake_policy</code></b></a></li> <li><a href="#command:configure_file"><b><code>configure_file</code></b></a></li> <li><a href="#command:CTEST_BUILD"><b><code>CTEST_BUILD</code></b></a></li> <li><a href="#command:CTEST_CONFIGURE"><b><code>CTEST_CONFIGURE</code></b></a></li> <li><a href="#command:CTEST_COVERAGE"><b><code>CTEST_COVERAGE</code></b></a></li> <li><a href="#command:CTEST_EMPTY_BINARY_DIRECTORY"><b><code>CTEST_EMPTY_BINARY_DIRECTORY</code></b></a></li> <li><a href="#command:CTEST_MEMCHECK"><b><code>CTEST_MEMCHECK</code></b></a></li> <li><a href="#command:CTEST_READ_CUSTOM_FILES"><b><code>CTEST_READ_CUSTOM_FILES</code></b></a></li> <li><a href="#command:CTEST_RUN_SCRIPT"><b><code>CTEST_RUN_SCRIPT</code></b></a></li> <li><a href="#command:CTEST_SLEEP"><b><code>CTEST_SLEEP</code></b></a></li> <li><a href="#command:CTEST_START"><b><code>CTEST_START</code></b></a></li> <li><a href="#command:CTEST_SUBMIT"><b><code>CTEST_SUBMIT</code></b></a></li> <li><a href="#command:CTEST_TEST"><b><code>CTEST_TEST</code></b></a></li> <li><a href="#command:CTEST_UPDATE"><b><code>CTEST_UPDATE</code></b></a></li> <li><a href="#command:else"><b><code>else</code></b></a></li> <li><a href="#command:elseif"><b><code>elseif</code></b></a></li> <li><a href="#command:endforeach"><b><code>endforeach</code></b></a></li> <li><a href="#command:endfunction"><b><code>endfunction</code></b></a></li> <li><a href="#command:endif"><b><code>endif</code></b></a></li> <li><a href="#command:endmacro"><b><code>endmacro</code></b></a></li> <li><a href="#command:endwhile"><b><code>endwhile</code></b></a></li> <li><a href="#command:exec_program"><b><code>exec_program</code></b></a></li> <li><a href="#command:execute_process"><b><code>execute_process</code></b></a></li> <li><a href="#command:file"><b><code>file</code></b></a></li> <li><a href="#command:find_file"><b><code>find_file</code></b></a></li> <li><a href="#command:find_library"><b><code>find_library</code></b></a></li> <li><a href="#command:find_package"><b><code>find_package</code></b></a></li> <li><a href="#command:find_path"><b><code>find_path</code></b></a></li> <li><a href="#command:find_program"><b><code>find_program</code></b></a></li> <li><a href="#command:foreach"><b><code>foreach</code></b></a></li> <li><a href="#command:function"><b><code>function</code></b></a></li> <li><a href="#command:get_cmake_property"><b><code>get_cmake_property</code></b></a></li> <li><a href="#command:get_directory_property"><b><code>get_directory_property</code></b></a></li> <li><a href="#command:get_filename_component"><b><code>get_filename_component</code></b></a></li> <li><a href="#command:get_property"><b><code>get_property</code></b></a></li> <li><a href="#command:if"><b><code>if</code></b></a></li> <li><a href="#command:include"><b><code>include</code></b></a></li> <li><a href="#command:list"><b><code>list</code></b></a></li> <li><a href="#command:macro"><b><code>macro</code></b></a></li> <li><a href="#command:make_directory"><b><code>make_directory</code></b></a></li> <li><a href="#command:mark_as_advanced"><b><code>mark_as_advanced</code></b></a></li> <li><a href="#command:math"><b><code>math</code></b></a></li> <li><a href="#command:message"><b><code>message</code></b></a></li> <li><a href="#command:option"><b><code>option</code></b></a></li> <li><a href="#command:remove"><b><code>remove</code></b></a></li> <li><a href="#command:return"><b><code>return</code></b></a></li> <li><a href="#command:separate_arguments"><b><code>separate_arguments</code></b></a></li> <li><a href="#command:set"><b><code>set</code></b></a></li> <li><a href="#command:set_directory_properties"><b><code>set_directory_properties</code></b></a></li> <li><a href="#command:set_property"><b><code>set_property</code></b></a></li> <li><a href="#command:site_name"><b><code>site_name</code></b></a></li> <li><a href="#command:string"><b><code>string</code></b></a></li> <li><a href="#command:variable_watch"><b><code>variable_watch</code></b></a></li> <li><a href="#command:while"><b><code>while</code></b></a></li> <li><a href="#command:write_file"><b><code>write_file</code></b></a></li></ul>
<ul>
<li>
--- 187,191 ----
<h2><a name="section_Commands"/>Commands</h2>
<ul>
! <li><a href="#command:break"><b><code>break</code></b></a></li> <li><a href="#command:build_name"><b><code>build_name</code></b></a></li> <li><a href="#command:cmake_minimum_required"><b><code>cmake_minimum_required</code></b></a></li> <li><a href="#command:cmake_policy"><b><code>cmake_policy</code></b></a></li> <li><a href="#command:configure_file"><b><code>configure_file</code></b></a></li> <li><a href="#command:ctest_build"><b><code>ctest_build</code></b></a></li> <li><a href="#command:ctest_configure"><b><code>ctest_configure</code></b></a></li> <li><a href="#command:ctest_coverage"><b><code>ctest_coverage</code></b></a></li> <li><a href="#command:ctest_empty_binary_directory"><b><code>ctest_empty_binary_directory</code></b></a></li> <li><a href="#command:ctest_memcheck"><b><code>ctest_memcheck</code></b></a></li> <li><a href="#command:ctest_read_custom_files"><b><code>ctest_read_custom_files</code></b></a></li> <li><a href="#command:ctest_run_script"><b><code>ctest_run_script</code></b></a></li> <li><a href="#command:ctest_sleep"><b><code>ctest_sleep</code></b></a></li> <li><a href="#command:ctest_start"><b><code>ctest_start</code></b></a></li> <li><a href="#command:ctest_submit"><b><code>ctest_submit</code></b></a></li> <li><a href="#command:CTEST_TEST"><b><code>CTEST_TEST</code></b></a></li> <li><a href="#command:ctest_update"><b><code>ctest_update</code></b></a></li> <li><a href="#command:else"><b><code>else</code></b></a></li> <li><a href="#command:elseif"><b><code>elseif</code></b></a></li> <li><a href="#command:endforeach"><b><code>endforeach</code></b></a></li> <li><a href="#command:endfunction"><b><code>endfunction</code></b></a></li> <li><a href="#command:endif"><b><code>endif</code></b></a></li> <li><a href="#command:endmacro"><b><code>endmacro</code></b></a></li> <li><a href="#command:endwhile"><b><code>endwhile</code></b></a></li> <li><a href="#command:exec_program"><b><code>exec_program</code></b></a></li> <li><a href="#command:execute_process"><b><code>execute_process</code></b></a></li> <li><a href="#command:file"><b><code>file</code></b></a></li> <li><a href="#command:find_file"><b><code>find_file</code></b></a></li> <li><a href="#command:find_library"><b><code>find_library</code></b></a></li> <li><a href="#command:find_package"><b><code>find_package</code></b></a></li> <li><a href="#command:find_path"><b><code>find_path</code></b></a></li> <li><a href="#command:find_program"><b><code>find_program</code></b></a></li> <li><a href="#command:foreach"><b><code>foreach</code></b></a></li> <li><a href="#command:function"><b><code>function</code></b></a></li> <li><a href="#command:get_cmake_property"><b><code>get_cmake_property</code></b></a></li> <li><a href="#command:get_directory_property"><b><code>get_directory_property</code></b></a></li> <li><a href="#command:get_filename_component"><b><code>get_filename_component</code></b></a></li> <li><a href="#command:get_property"><b><code>get_property</code></b></a></li> <li><a href="#command:if"><b><code>if</code></b></a></li> <li><a href="#command:include"><b><code>include</code></b></a></li> <li><a href="#command:list"><b><code>list</code></b></a></li> <li><a href="#command:macro"><b><code>macro</code></b></a></li> <li><a href="#command:make_directory"><b><code>make_directory</code></b></a></li> <li><a href="#command:mark_as_advanced"><b><code>mark_as_advanced</code></b></a></li> <li><a href="#command:math"><b><code>math</code></b></a></li> <li><a href="#command:message"><b><code>message</code></b></a></li> <li><a href="#command:option"><b><code>option</code></b></a></li> <li><a href="#command:remove"><b><code>remove</code></b></a></li> <li><a href="#command:return"><b><code>return</code></b></a></li> <li><a href="#command:separate_arguments"><b><code>separate_arguments</code></b></a></li> <li><a href="#command:set"><b><code>set</code></b></a></li> <li><a href="#command:set_directory_properties"><b><code>set_directory_properties</code></b></a></li> <li><a href="#command:set_property"><b><code>set_property</code></b></a></li> <li><a href="#command:site_name"><b><code>site_name</code></b></a></li> <li><a href="#command:string"><b><code>string</code></b></a></li> <li><a href="#command:variable_watch"><b><code>variable_watch</code></b></a></li> <li><a href="#command:while"><b><code>while</code></b></a></li> <li><a href="#command:write_file"><b><code>write_file</code></b></a></li></ul>
<ul>
<li>
***************
*** 219,269 ****
</li>
<li>
! <a name="command:CTEST_BUILD"><b><code>CTEST_BUILD</code></b></a>: Builds the repository.<br>
! <pre> CTEST_BUILD([BUILD build_dir] [RETURN_VALUE res])<br></pre>
<p>Builds the given build directory and stores results in Build.xml.
</li>
<li>
! <a name="command:CTEST_CONFIGURE"><b><code>CTEST_CONFIGURE</code></b></a>: Configures the repository.<br>
! <pre> CTEST_CONFIGURE(BUILD build_dir RETURN_VALUE res)<br></pre>
<p>Configures the given build directory and stores results in Configure.xml. The second argument is a variable that will hold return value.
</li>
<li>
! <a name="command:CTEST_COVERAGE"><b><code>CTEST_COVERAGE</code></b></a>: Tests the repository.<br>
! <pre> CTEST_COVERAGE([BUILD build_dir] [RETURN_VALUE res])<br></pre>
<p>Perform the coverage of the given build directory and stores results in Coverage.xml. The second argument is a variable that will hold value.
</li>
<li>
! <a name="command:CTEST_EMPTY_BINARY_DIRECTORY"><b><code>CTEST_EMPTY_BINARY_DIRECTORY</code></b></a>: empties the binary directory<br>
! <pre> CTEST_EMPTY_BINARY_DIRECTORY( directory )<br></pre>
<p>Removes a binary directory. This command will perform some checks prior to deleting the directory in an attempt to avoid malicious or accidental directory deletion.
</li>
<li>
! <a name="command:CTEST_MEMCHECK"><b><code>CTEST_MEMCHECK</code></b></a>: Tests the repository.<br>
! <pre> CTEST_MEMCHECK([BUILD build_dir] [RETURN_VALUE res])<br></pre>
<p>Performs a memory checking of tests in the given build directory and stores results in MemCheck.xml. The second argument is a variable that will hold value.
</li>
<li>
! <a name="command:CTEST_READ_CUSTOM_FILES"><b><code>CTEST_READ_CUSTOM_FILES</code></b></a>: read CTestCustom files.<br>
! <pre> CTEST_READ_CUSTOM_FILES( directory ... )<br></pre>
<p>Read all the CTestCustom.ctest or CTestCustom.cmake files from the given directory.
</li>
<li>
! <a name="command:CTEST_RUN_SCRIPT"><b><code>CTEST_RUN_SCRIPT</code></b></a>: runs a ctest -S script<br>
! <pre> CTEST_RUN_SCRIPT([NEW_PROCESS] script_file_name script_file_name1 <br> script_file_name2 ...)<br></pre>
<p>Runs a script or scripts much like if it was run from ctest -S. If no argument is provided then the current script is run using the current settings of the variables. If NEW_PROCESS is specified then each script will be run in a seperate process.
</li>
<li>
! <a name="command:CTEST_SLEEP"><b><code>CTEST_SLEEP</code></b></a>: sleeps for some amount of time<br>
! <pre> CTEST_SLEEP( seconds )<br> CTEST_SLEEP( time1 duration time2 )<br></pre>
<p>With one argument it will sleep for a given number of seconds. With three arguments it will wait for time2 - time1 - duration seconds.
</li>
<li>
! <a name="command:CTEST_START"><b><code>CTEST_START</code></b></a>: Starts the testing for a given model<br>
! <pre> CTEST_START(Model [TRACK <track>] [source [binary]])<br></pre>
<p>Starts the testing for a given model. The command should be called after the binary directory is initialized. If the 'source' and 'binary' directory are not specified, it reads the CTEST_SOURCE_DIRECTORY and CTEST_BINARY_DIRECTORY. If the track is specified, the submissions will go to the specified track.
</li>
<li>
! <a name="command:CTEST_SUBMIT"><b><code>CTEST_SUBMIT</code></b></a>: Submits the repository.<br>
! <pre> CTEST_SUBMIT([RETURN_VALUE res])<br></pre>
<p>Submits the test results for the project.
</li>
--- 219,269 ----
</li>
<li>
! <a name="command:ctest_build"><b><code>ctest_build</code></b></a>: Builds the repository.<br>
! <pre> ctest_build([BUILD build_dir] [RETURN_VALUE res])<br></pre>
<p>Builds the given build directory and stores results in Build.xml.
</li>
<li>
! <a name="command:ctest_configure"><b><code>ctest_configure</code></b></a>: Configures the repository.<br>
! <pre> ctest_configure(BUILD build_dir RETURN_VALUE res)<br></pre>
<p>Configures the given build directory and stores results in Configure.xml. The second argument is a variable that will hold return value.
</li>
<li>
! <a name="command:ctest_coverage"><b><code>ctest_coverage</code></b></a>: Tests the repository.<br>
! <pre> ctest_coverage([BUILD build_dir] [RETURN_VALUE res])<br></pre>
<p>Perform the coverage of the given build directory and stores results in Coverage.xml. The second argument is a variable that will hold value.
</li>
<li>
! <a name="command:ctest_empty_binary_directory"><b><code>ctest_empty_binary_directory</code></b></a>: empties the binary directory<br>
! <pre> ctest_empty_binary_directory( directory )<br></pre>
<p>Removes a binary directory. This command will perform some checks prior to deleting the directory in an attempt to avoid malicious or accidental directory deletion.
</li>
<li>
! <a name="command:ctest_memcheck"><b><code>ctest_memcheck</code></b></a>: Tests the repository.<br>
! <pre> ctest_memcheck([BUILD build_dir] [RETURN_VALUE res])<br></pre>
<p>Performs a memory checking of tests in the given build directory and stores results in MemCheck.xml. The second argument is a variable that will hold value.
</li>
<li>
! <a name="command:ctest_read_custom_files"><b><code>ctest_read_custom_files</code></b></a>: read CTestCustom files.<br>
! <pre> ctest_read_custom_files( directory ... )<br></pre>
<p>Read all the CTestCustom.ctest or CTestCustom.cmake files from the given directory.
</li>
<li>
! <a name="command:ctest_run_script"><b><code>ctest_run_script</code></b></a>: runs a ctest -S script<br>
! <pre> ctest_run_script([NEW_PROCESS] script_file_name script_file_name1 <br> script_file_name2 ...)<br></pre>
<p>Runs a script or scripts much like if it was run from ctest -S. If no argument is provided then the current script is run using the current settings of the variables. If NEW_PROCESS is specified then each script will be run in a seperate process.
</li>
<li>
! <a name="command:ctest_sleep"><b><code>ctest_sleep</code></b></a>: sleeps for some amount of time<br>
! <pre> ctest_sleep( seconds )<br> ctest_sleep( time1 duration time2 )<br></pre>
<p>With one argument it will sleep for a given number of seconds. With three arguments it will wait for time2 - time1 - duration seconds.
</li>
<li>
! <a name="command:ctest_start"><b><code>ctest_start</code></b></a>: Starts the testing for a given model<br>
! <pre> ctest_start(Model [TRACK <track>] [source [binary]])<br></pre>
<p>Starts the testing for a given model. The command should be called after the binary directory is initialized. If the 'source' and 'binary' directory are not specified, it reads the CTEST_SOURCE_DIRECTORY and CTEST_BINARY_DIRECTORY. If the track is specified, the submissions will go to the specified track.
</li>
<li>
! <a name="command:ctest_submit"><b><code>ctest_submit</code></b></a>: Submits the repository.<br>
! <pre> ctest_submit([RETURN_VALUE res])<br></pre>
<p>Submits the test results for the project.
</li>
***************
*** 274,279 ****
</li>
<li>
! <a name="command:CTEST_UPDATE"><b><code>CTEST_UPDATE</code></b></a>: Updates the repository.<br>
! <pre> CTEST_UPDATE([SOURCE source] [RETURN_VALUE res])<br></pre>
<p>Updates the given source directory and stores results in Update.xml. The second argument is a variable that will hold the number of files modified. If there is a problem, the variable will be -1.
</li>
--- 274,279 ----
</li>
<li>
! <a name="command:ctest_update"><b><code>ctest_update</code></b></a>: Updates the repository.<br>
! <pre> ctest_update([SOURCE source] [RETURN_VALUE res])<br></pre>
<p>Updates the given source directory and stores results in Update.xml. The second argument is a variable that will hold the number of files modified. If there is a problem, the variable will be -1.
</li>
***************
*** 334,364 ****
<a name="command:find_file"><b><code>find_file</code></b></a>: Find the full path to a file.<br>
<pre> find_path(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_path(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_path(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a full path to named file. A cache entry named by <VAR> is created to store the result of this command. If the full path to a file is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_path is invoked with the same variable. The name of the full path to a file that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> INCLUDE<br></pre>
! <p>4. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_INCLUDE_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>5. Search the paths specified after PATHS or in the short-hand version of the command.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_path(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_path(<VAR> NAMES name)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.
</li>
<li>
<a name="command:find_library"><b><code>find_library</code></b></a>: Find a library.<br>
<pre> find_library(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_library(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_library(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a library. A cache entry named by <VAR> is created to store the result of this command. If the library is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_library is invoked with the same variable. The name of the library that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_LIBRARY_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_LIBRARY_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> LIB<br></pre>
! <p>4. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_LIBRARY_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>5. Search the paths specified after PATHS or in the short-hand version of the command.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_LIBRARY. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_library(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_library(<VAR> NAMES name)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.<br><p>If the library found is a framework, then VAR will be set to the full path to the framework <fullPath>/A.framework. When a full path to a framework is used as a library, CMake will use a -framework A, and a -F<fullPath> to link the framework to the target.
</li>
<li>
<a name="command:find_package"><b><code>find_package</code></b></a>: Load settings for an external project.<br>
<pre> find_package(<package> [major[.minor[.patch]]] [EXACT] [QUIET]<br> [[REQUIRED|COMPONENTS] [components...]])<br></pre>
! <p>Finds and loads settings from an external project. <package>_FOUND will be set to indicate whether the package was found. When the package is found package-specific information is provided through variables documented by the package itself. The QUIET option disables messages if the package cannot be found. The REQUIRED option stops processing with an error message if the package cannot be found. A package-specific list of components may be listed after the REQUIRED option or after the COMPONENTS option if no REQUIRED option is given. The "[major[.minor[.patch]]]" version argument specifies a desired version with which the package found should be compatible. The EXACT option requests that the version be matched exactly. Version support is currently provided only on a package-by-package basis (details below).<br><p>User code should generally look for packages using the above simple signature. The remainder of this command documentation specifies the full command signature and details of the search process. Project maintainers wishing to provide a package to be found by this command are encouraged to read on.<br><p>The command has two modes by which it searches for packages: "Module" mode and "Config" mode. Module mode is available when the command is invoked with the above reduced signature. CMake searches for a file called "Find<package>.cmake" in the CMAKE_MODULE_PATH followed by the CMake installation. If the file is found, it is read and processed by CMake. It is responsible for finding the package, checking the version, and producing any needed messages. Many find-modules provide limited or no support for versioning; check the module documentation. If no module is found the command proceeds to Config mode.<br><p>The complete Config mode command signature is:<br><pre> find_package(<package> [major[.minor[.patch]]] [EXACT] [QUIET]<br> [[REQUIRED|COMPONENTS] [components...]] [NO_MODULE]<br> [NAMES name1 [name2 ...]]<br> [CONFIGS config1 [config2 ...]]<br> [PATHS path1 [path2 ... ]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_BUILDS_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH])<br></pre>
<p>The NO_MODULE option may be used to skip Module mode explicitly. It is also implied by use of options not specified in the reduced signature. <br><p>Config mode attempts to locate a configuration file provided by the package to be found. A cache entry called <package>_DIR is created to hold the directory containing the file. By default the command searches for a package with the name <package>. If the NAMES option is given the names following it are used instead of <package>. The command searches for a file called "<name>Config.cmake" or "<lower-case-name>-config.cmake" for each name specified. A replacement set of possible configuration file names may be given using the CONFIGS option. The search procedure is specified below. Once found, the configuration file is read and processed by CMake. Since the file is provided by the package it already knows the location of package contents. The full path to the configuration file is stored in the cmake variable <package>_CONFIG.<br><p>If the package configuration file cannot be found CMake will generate an error describing the problem unless the QUIET argument is specified. If REQUIRED is specified and the package is not found a fatal error is generated and the configure step stops executing. If <package>_DIR has been set to a directory not containing a configuration file a fatal error is always generated because user intervention is required.<br><p>When the "[major[.minor[.patch]]]" version argument is specified Config mode will only find a version of the package that claims compatibility with the requested version. If the EXACT option is given only a version of the package claiming an exact match of the requested version may be found. CMake does not establish any convention for the meaning of version numbers. Package version numbers are checked by "version" files provided by the packages themselves. For a candidate package confguration file "<config-file>.cmake" the corresponding version file is located next to it and named either "<config-file>-version.cmake" or "<config-file>Version.cmake". If no such version file is available then the configuration file is assumed to not be compatible with any requested version. When a version file is found it is loaded to check the requested version number. The version file is loaded in a nested scope in which the following variables have been defined:<br><pre> PACKAGE_FIND_NAME = the <package> name<br> PACKAGE_FIND_VERSION = full requested version string<br> PACKAGE_FIND_VERSION_MAJOR = requested major version, if any<br> PACKAGE_FIND_VERSION_MINOR = requested minor version, if any<br> PACKAGE_FIND_VERSION_PATCH = requested patch version, if any<br></pre>
<p>The version file checks whether it satisfies the requested version and sets these variables:<br><pre> PACKAGE_VERSION = package version (major[.minor[.patch]])<br> PACKAGE_VERSION_EXACT = true if version is exact match<br> PACKAGE_VERSION_COMPATIBLE = true if version is compatible<br></pre>
--- 334,364 ----
<a name="command:find_file"><b><code>find_file</code></b></a>: Find the full path to a file.<br>
<pre> find_path(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_path(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_path(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [HINTS path1 [path2 ... ENV var]]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a full path to named file. A cache entry named by <VAR> is created to store the result of this command. If the full path to a file is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_path is invoked with the same variable. The name of the full path to a file that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the HINTS or PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> INCLUDE<br></pre>
! <p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_INCLUDE_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>6. Search the paths specified by the PATHS option or in the short-hand version of the command. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_path(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_path(<VAR> NAMES name)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.
</li>
<li>
<a name="command:find_library"><b><code>find_library</code></b></a>: Find a library.<br>
<pre> find_library(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_library(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_library(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [HINTS path1 [path2 ... ENV var]]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a library. A cache entry named by <VAR> is created to store the result of this command. If the library is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_library is invoked with the same variable. The name of the library that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the HINTS or PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_LIBRARY_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_LIBRARY_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> LIB<br></pre>
! <p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/lib for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_LIBRARY_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>6. Search the paths specified by the PATHS option or in the short-hand version of the command. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_LIBRARY. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_library(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_library(<VAR> NAMES name)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.<br><p>If the library found is a framework, then VAR will be set to the full path to the framework <fullPath>/A.framework. When a full path to a framework is used as a library, CMake will use a -framework A, and a -F<fullPath> to link the framework to the target.
</li>
<li>
<a name="command:find_package"><b><code>find_package</code></b></a>: Load settings for an external project.<br>
<pre> find_package(<package> [major[.minor[.patch]]] [EXACT] [QUIET]<br> [[REQUIRED|COMPONENTS] [components...]])<br></pre>
! <p>Finds and loads settings from an external project. <package>_FOUND will be set to indicate whether the package was found. When the package is found package-specific information is provided through variables documented by the package itself. The QUIET option disables messages if the package cannot be found. The REQUIRED option stops processing with an error message if the package cannot be found. A package-specific list of components may be listed after the REQUIRED option or after the COMPONENTS option if no REQUIRED option is given. The "[major[.minor[.patch]]]" version argument specifies a desired version with which the package found should be compatible. The EXACT option requests that the version be matched exactly. Version support is currently provided only on a package-by-package basis (details below).<br><p>User code should generally look for packages using the above simple signature. The remainder of this command documentation specifies the full command signature and details of the search process. Project maintainers wishing to provide a package to be found by this command are encouraged to read on.<br><p>The command has two modes by which it searches for packages: "Module" mode and "Config" mode. Module mode is available when the command is invoked with the above reduced signature. CMake searches for a file called "Find<package>.cmake" in the CMAKE_MODULE_PATH followed by the CMake installation. If the file is found, it is read and processed by CMake. It is responsible for finding the package, checking the version, and producing any needed messages. Many find-modules provide limited or no support for versioning; check the module documentation. If no module is found the command proceeds to Config mode.<br><p>The complete Config mode command signature is:<br><pre> find_package(<package> [major[.minor[.patch]]] [EXACT] [QUIET]<br> [[REQUIRED|COMPONENTS] [components...]] [NO_MODULE]<br> [NAMES name1 [name2 ...]]<br> [CONFIGS config1 [config2 ...]]<br> [HINTS path1 [path2 ... ]]<br> [PATHS path1 [path2 ... ]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_BUILDS_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH])<br></pre>
<p>The NO_MODULE option may be used to skip Module mode explicitly. It is also implied by use of options not specified in the reduced signature. <br><p>Config mode attempts to locate a configuration file provided by the package to be found. A cache entry called <package>_DIR is created to hold the directory containing the file. By default the command searches for a package with the name <package>. If the NAMES option is given the names following it are used instead of <package>. The command searches for a file called "<name>Config.cmake" or "<lower-case-name>-config.cmake" for each name specified. A replacement set of possible configuration file names may be given using the CONFIGS option. The search procedure is specified below. Once found, the configuration file is read and processed by CMake. Since the file is provided by the package it already knows the location of package contents. The full path to the configuration file is stored in the cmake variable <package>_CONFIG.<br><p>If the package configuration file cannot be found CMake will generate an error describing the problem unless the QUIET argument is specified. If REQUIRED is specified and the package is not found a fatal error is generated and the configure step stops executing. If <package>_DIR has been set to a directory not containing a configuration file a fatal error is always generated because user intervention is required.<br><p>When the "[major[.minor[.patch]]]" version argument is specified Config mode will only find a version of the package that claims compatibility with the requested version. If the EXACT option is given only a version of the package claiming an exact match of the requested version may be found. CMake does not establish any convention for the meaning of version numbers. Package version numbers are checked by "version" files provided by the packages themselves. For a candidate package confguration file "<config-file>.cmake" the corresponding version file is located next to it and named either "<config-file>-version.cmake" or "<config-file>Version.cmake". If no such version file is available then the configuration file is assumed to not be compatible with any requested version. When a version file is found it is loaded to check the requested version number. The version file is loaded in a nested scope in which the following variables have been defined:<br><pre> PACKAGE_FIND_NAME = the <package> name<br> PACKAGE_FIND_VERSION = full requested version string<br> PACKAGE_FIND_VERSION_MAJOR = requested major version, if any<br> PACKAGE_FIND_VERSION_MINOR = requested minor version, if any<br> PACKAGE_FIND_VERSION_PATCH = requested patch version, if any<br></pre>
<p>The version file checks whether it satisfies the requested version and sets these variables:<br><pre> PACKAGE_VERSION = package version (major[.minor[.patch]])<br> PACKAGE_VERSION_EXACT = true if version is exact match<br> PACKAGE_VERSION_COMPATIBLE = true if version is compatible<br></pre>
***************
*** 367,404 ****
<p>in order to find a package. Package maintainers providing CMake package configuration files are encouraged to name and install them such that the procedure outlined below will find them without requiring use of additional options.<br><p>CMake constructs a set of possible installation prefixes for the package. Under each prefix several directories are searched for a configuration file. The tables below show the directories searched. Each entry is meant for installation trees following Windows (W), UNIX (U), or Apple (A) conventions.<br><pre> <prefix>/ (W)<br> <prefix>/(cmake|CMake)/ (W)<br> <prefix>/(share|lib)/<name>*/ (U)<br> <prefix>/(share|lib)/<name>*/(cmake|CMake)/ (U)<br></pre>
<p>On systems supporting OS X Frameworks and Application Bundles the following directories are searched for frameworks or bundles containing a configuration file:<br><pre> <prefix>/<name>.framework/Resources/ (A)<br> <prefix>/<name>.framework/Resources/CMake/ (A)<br> <prefix>/<name>.framework/Versions/*/Resources/ (A)<br> <prefix>/<name>.framework/Versions/*/Resources/CMake/ (A)<br> <prefix>/<name>.app/Contents/Resources/ (A)<br> <prefix>/<name>.app/Contents/Resources/CMake/ (A)<br></pre>
! <p>In all cases the <name> is treated as case-insensitive and corresponds to any of the names specified (<package> or names given by NAMES). If PATH_SUFFIXES is specified the suffixes are appended to each (W) or (U) directory entry one-by-one.<br><p>This set of directories is intended to work in cooperation with projects that provide configuration files in their installation trees. Directories above marked with (W) are intended for installations on Windows where the prefix may point at the top of an application's installation directory. Those marked with (U) are intended for installations on UNIX platforms where the prefix is shared by multiple packages. This is merely a convention, so all (W) and (U) directories are still searched on all platforms. Directories marked with (A) are intended for installations on Apple platforms. The cmake variables CMAKE_FIND_FRAMEWORK and CMAKE_FIND_APPBUNDLE determine the order of preference as specified below.<br><p>The set of installation prefixes is constructed using the following steps. If NO_DEFAULT_PATH is specified steps 1-5 are skipped.<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> CMAKE_PREFIX_PATH<br> CMAKE_FRAMEWORK_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> CMAKE_PREFIX_PATH<br> CMAKE_FRAMEWORK_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is passed. Path entries ending in "/bin" or "/sbin" are automatically converted to their parent directories.<br><pre> PATH<br></pre>
! <p>4. Search project build trees recently configured in a CMake GUI. This can be skipped if NO_CMAKE_BUILDS_PATH is passed. It is intended for the case when a user is building multiple dependent projects one after another.<br><p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br> CMAKE_SYSTEM_APPBUNDLE_PATH<br></pre>
! <p>6. Search paths specified by the PATHS option.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_PACKAGE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_package(<package> PATHS paths... NO_DEFAULT_PATH)<br> find_package(<package>)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.
</li>
<li>
<a name="command:find_path"><b><code>find_path</code></b></a>: Find the directory containing a file.<br>
<pre> find_path(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_path(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_path(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a directory containing the named file. A cache entry named by <VAR> is created to store the result of this command. If the file in a directory is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_path is invoked with the same variable. The name of the file in a directory that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> INCLUDE<br></pre>
! <p>4. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_INCLUDE_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>5. Search the paths specified after PATHS or in the short-hand version of the command.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_path(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_path(<VAR> NAMES name)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.<br><p>When searching for frameworks, if the file is specified as A/b.h, then the framework search will look for A.framework/Headers/b.h. If that is found the path will be set to the path to the framework. CMake will convert this to the correct -F option to include the file.
</li>
<li>
<a name="command:find_program"><b><code>find_program</code></b></a>: Find an executable program.<br>
<pre> find_program(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_program(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_program(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a program. A cache entry named by <VAR> is created to store the result of this command. If the program is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_program is invoked with the same variable. The name of the program that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search cmake specific environment variables. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_PROGRAM_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>2. Search cmake variables with the same names as the cmake specific environment variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_PROGRAM_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>3. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> <br></pre>
! <p>4. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_PROGRAM_PATH<br> CMAKE_SYSTEM_APPBUNDLE_PATH<br></pre>
! <p>5. Search the paths specified after PATHS or in the short-hand version of the command.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_PROGRAM. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The reason the paths listed in the call to the command are searched last is that most users of CMake would expect things to be found first in the locations specified by their environment. Projects may override this behavior by simply calling the command twice:<br><pre> find_program(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_program(<VAR> NAMES name)<br></pre>
! <p>Once one of these calls succeeds the result variable will be set and stored in the cache so that neither call will search again.
</li>
<li>
--- 367,404 ----
<p>in order to find a package. Package maintainers providing CMake package configuration files are encouraged to name and install them such that the procedure outlined below will find them without requiring use of additional options.<br><p>CMake constructs a set of possible installation prefixes for the package. Under each prefix several directories are searched for a configuration file. The tables below show the directories searched. Each entry is meant for installation trees following Windows (W), UNIX (U), or Apple (A) conventions.<br><pre> <prefix>/ (W)<br> <prefix>/(cmake|CMake)/ (W)<br> <prefix>/(share|lib)/<name>*/ (U)<br> <prefix>/(share|lib)/<name>*/(cmake|CMake)/ (U)<br></pre>
<p>On systems supporting OS X Frameworks and Application Bundles the following directories are searched for frameworks or bundles containing a configuration file:<br><pre> <prefix>/<name>.framework/Resources/ (A)<br> <prefix>/<name>.framework/Resources/CMake/ (A)<br> <prefix>/<name>.framework/Versions/*/Resources/ (A)<br> <prefix>/<name>.framework/Versions/*/Resources/CMake/ (A)<br> <prefix>/<name>.app/Contents/Resources/ (A)<br> <prefix>/<name>.app/Contents/Resources/CMake/ (A)<br></pre>
! <p>In all cases the <name> is treated as case-insensitive and corresponds to any of the names specified (<package> or names given by NAMES). If PATH_SUFFIXES is specified the suffixes are appended to each (W) or (U) directory entry one-by-one.<br><p>This set of directories is intended to work in cooperation with projects that provide configuration files in their installation trees. Directories above marked with (W) are intended for installations on Windows where the prefix may point at the top of an application's installation directory. Those marked with (U) are intended for installations on UNIX platforms where the prefix is shared by multiple packages. This is merely a convention, so all (W) and (U) directories are still searched on all platforms. Directories marked with (A) are intended for installations on Apple platforms. The cmake variables CMAKE_FIND_FRAMEWORK and CMAKE_FIND_APPBUNDLE determine the order of preference as specified below.<br><p>The set of installation prefixes is constructed using the following steps. If NO_DEFAULT_PATH is specified all NO_* options are enabled.<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> CMAKE_PREFIX_PATH<br> CMAKE_FRAMEWORK_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> CMAKE_PREFIX_PATH<br> CMAKE_FRAMEWORK_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>3. Search paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is passed. Path entries ending in "/bin" or "/sbin" are automatically converted to their parent directories.<br><pre> PATH<br></pre>
! <p>5. Search project build trees recently configured in a CMake GUI. This can be skipped if NO_CMAKE_BUILDS_PATH is passed. It is intended for the case when a user is building multiple dependent projects one after another.<br><p>6. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br> CMAKE_SYSTEM_APPBUNDLE_PATH<br></pre>
! <p>7. Search paths specified by the PATHS option. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_PACKAGE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_package(<package> PATHS paths... NO_DEFAULT_PATH)<br> find_package(<package>)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.
</li>
<li>
<a name="command:find_path"><b><code>find_path</code></b></a>: Find the directory containing a file.<br>
<pre> find_path(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_path(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_path(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [HINTS path1 [path2 ... ENV var]]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a directory containing the named file. A cache entry named by <VAR> is created to store the result of this command. If the file in a directory is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_path is invoked with the same variable. The name of the file in a directory that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the HINTS or PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_INCLUDE_PATH<br> CMAKE_FRAMEWORK_PATH<br></pre>
! <p>3. Search the paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> INCLUDE<br></pre>
! <p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/include for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_INCLUDE_PATH<br> CMAKE_SYSTEM_FRAMEWORK_PATH<br></pre>
! <p>6. Search the paths specified by the PATHS option or in the short-hand version of the command. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_INCLUDE. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_path(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_path(<VAR> NAMES name)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.<br><p>When searching for frameworks, if the file is specified as A/b.h, then the framework search will look for A.framework/Headers/b.h. If that is found the path will be set to the path to the framework. CMake will convert this to the correct -F option to include the file.
</li>
<li>
<a name="command:find_program"><b><code>find_program</code></b></a>: Find an executable program.<br>
<pre> find_program(<VAR> name1 [path1 path2 ...])<br></pre>
! <p>This is the short-hand signature for the command that is sufficient in many cases. It is the same as find_program(<VAR> name1 [PATHS path1 path2 ...])<br><pre> find_program(<br> <VAR><br> name | NAMES name1 [name2 ...]<br> [HINTS path1 [path2 ... ENV var]]<br> [PATHS path1 [path2 ... ENV var]]<br> [PATH_SUFFIXES suffix1 [suffix2 ...]]<br> [DOC "cache documentation string"]<br> [NO_DEFAULT_PATH]<br> [NO_CMAKE_ENVIRONMENT_PATH]<br> [NO_CMAKE_PATH]<br> [NO_SYSTEM_ENVIRONMENT_PATH]<br> [NO_CMAKE_SYSTEM_PATH]<br> [CMAKE_FIND_ROOT_PATH_BOTH |<br> ONLY_CMAKE_FIND_ROOT_PATH |<br> NO_CMAKE_FIND_ROOT_PATH]<br> )<br></pre>
! <p>This command is used to find a program. A cache entry named by <VAR> is created to store the result of this command. If the program is found the result is stored in the variable and the search will not be repeated unless the variable is cleared. If nothing is found, the result will be <VAR>-NOTFOUND, and the search will be attempted again the next time find_program is invoked with the same variable. The name of the program that is searched for is specified by the names listed after the NAMES argument. Additional search locations can be specified after the PATHS argument. If ENV var is found in the HINTS or PATHS section the environment variable var will be read and converted from a system environment variable to a cmake style list of paths. For example ENV PATH would be a way to list the system path variable. The argument after DOC will be used for the documentation string in the cache. PATH_SUFFIXES can be used to give sub directories that will be appended to the search paths.<br><p>If NO_DEFAULT_PATH is specified, then no additional paths are added to the search. If NO_DEFAULT_PATH is not specified, the search process is as follows:<br><p>1. Search paths specified in cmake-specific cache variables. These are intended to be used on the command line with a -DVAR=value. This can be skipped if NO_CMAKE_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_PROGRAM_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>2. Search paths specified in cmake-specific environment variables. These are intended to be set in the user's shell configuration. This can be skipped if NO_CMAKE_ENVIRONMENT_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_PREFIX_PATH<br> CMAKE_PROGRAM_PATH<br> CMAKE_APPBUNDLE_PATH<br></pre>
! <p>3. Search the paths specified by the HINTS option. These should be paths computed by system introspection, such as a hint provided by the location of another item already found. Hard-coded guesses should be specified with the PATHS option.<br><p>4. Search the standard system environment variables. This can be skipped if NO_SYSTEM_ENVIRONMENT_PATH is an argument.<br><pre> PATH<br> <br></pre>
! <p>5. Search cmake variables defined in the Platform files for the current system. This can be skipped if NO_CMAKE_SYSTEM_PATH is passed.<br><pre> <prefix>/[s]bin for each <prefix> in CMAKE_SYSTEM_PREFIX_PATH<br> CMAKE_SYSTEM_PROGRAM_PATH<br> CMAKE_SYSTEM_APPBUNDLE_PATH<br></pre>
! <p>6. Search the paths specified by the PATHS option or in the short-hand version of the command. These are typically hard-coded guesses.<br><p>On Darwin or systems supporting OS X Frameworks, the cmake variable CMAKE_FIND_FRAMEWORK can be set to empty or one of the following:<br><pre> "FIRST" - Try to find frameworks before standard<br> libraries or headers. This is the default on Darwin.<br> "LAST" - Try to find frameworks after standard<br> libraries or headers.<br> "ONLY" - Only try to find frameworks.<br> "NEVER". - Never try to find frameworks.<br></pre>
<p>On Darwin or systems supporting OS X Application Bundles, the cmake variable CMAKE_FIND_APPBUNDLE can be set to empty or one of the following:<br><pre> "FIRST" - Try to find application bundles before standard<br> programs. This is the default on Darwin.<br> "LAST" - Try to find application bundles after standard<br> programs.<br> "ONLY" - Only try to find application bundles.<br> "NEVER". - Never try to find application bundles.<br></pre>
! <p>The CMake variable CMAKE_FIND_ROOT_PATH specifies one or more directories to be prepended to all other search directories. This effectively "re-roots" the entire search under given locations. By default it is empty. It is especially useful when cross-compiling to point to the root directory of the target environment and CMake will search there too. By default at first the directories listed in CMAKE_FIND_ROOT_PATH and then the non-rooted directories will be searched. The default behavior can be adjusted by setting CMAKE_FIND_ROOT_PATH_MODE_PROGRAM. This behavior can be manually overridden on a per-call basis. By using CMAKE_FIND_ROOT_PATH_BOTH the search order will be as described above. If NO_CMAKE_FIND_ROOT_PATH is used then CMAKE_FIND_ROOT_PATH will not be used. If ONLY_CMAKE_FIND_ROOT_PATH is used then only the re-rooted directories will be searched.<br><p>The default search order is designed to be most-specific to least-specific for common use cases. Projects may override the order by simply calling the command multiple times and using the NO_* options:<br><pre> find_program(<VAR> NAMES name PATHS paths... NO_DEFAULT_PATH)<br> find_program(<VAR> NAMES name)<br></pre>
! <p>Once one of the calls succeeds the result variable will be set and stored in the cache so that no call will search again.
</li>
<li>
***************
*** 415,419 ****
<a name="command:get_cmake_property"><b><code>get_cmake_property</code></b></a>: Get a property of the CMake instance.<br>
<pre> get_cmake_property(VAR property)<br></pre>
! <p>Get a property from the CMake instance. The value of the property is stored in the variable VAR. If the property is not found, CMake will report an error. Some supported properties include: VARIABLES, CACHE_VARIABLES, COMMANDS, and MACROS.
</li>
<li>
--- 415,419 ----
<a name="command:get_cmake_property"><b><code>get_cmake_property</code></b></a>: Get a property of the CMake instance.<br>
<pre> get_cmake_property(VAR property)<br></pre>
! <p>Get a property from the CMake instance. The value of the property is stored in the variable VAR. If the property is not found, CMake will report an error. Some supported properties include: VARIABLES, CACHE_VARIABLES, COMMANDS, MACROS, and COMPONENTS.
</li>
<li>
More information about the Cmake-commits
mailing list