diff options
Diffstat (limited to 'Help')
| -rw-r--r-- | Help/command/add_definitions.rst | 6 | ||||
| -rw-r--r-- | Help/command/add_test.rst | 86 | ||||
| -rw-r--r-- | Help/command/install.rst | 329 | ||||
| -rw-r--r-- | Help/manual/cmake-buildsystem.7.rst | 10 | ||||
| -rw-r--r-- | Help/policy/CMP0043.rst | 8 | ||||
| -rw-r--r-- | Help/release/3.0.0.rst (renamed from Help/release/3.0.rst) | 20 | ||||
| -rw-r--r-- | Help/release/dev/0-sample-topic.rst | 7 | ||||
| -rw-r--r-- | Help/release/dev/Boost_NAMESPACE.rst | 5 | ||||
| -rw-r--r-- | Help/release/index.rst | 4 | ||||
| -rw-r--r-- | Help/variable/CMAKE_TWEAK_VERSION.rst | 10 | ||||
| -rw-r--r-- | Help/variable/CMAKE_VERSION.rst | 19 |
11 files changed, 263 insertions, 241 deletions
diff --git a/Help/command/add_definitions.rst b/Help/command/add_definitions.rst index a9a6bf5..2965c37 100644 --- a/Help/command/add_definitions.rst +++ b/Help/command/add_definitions.rst @@ -21,7 +21,5 @@ backwards compatibility. See documentation of the properties for details on adding preprocessor definitions to specific scopes and configurations. -Arguments to ``add_definitions`` may use "generator expressions" with -the syntax "$<...>". See the :manual:`cmake-generator-expressions(7)` -manual for available expressions. See the :manual:`cmake-buildsystem(7)` -manual for more on defining buildsystem properties. +See the :manual:`cmake-buildsystem(7)` manual for more on defining +buildsystem properties. diff --git a/Help/command/add_test.rst b/Help/command/add_test.rst index 5714559..7e7e6bd 100644 --- a/Help/command/add_test.rst +++ b/Help/command/add_test.rst @@ -1,69 +1,59 @@ add_test -------- -Add a test to the project with the specified arguments. +Add a test to the project to be run by :manual:`ctest(1)`. :: - add_test(testname Exename arg1 arg2 ... ) + add_test(NAME <name> COMMAND <command> [<arg>...] + [CONFIGURATIONS <config>...] + [WORKING_DIRECTORY <dir>]) -If the ENABLE_TESTING command has been run, this command adds a test -target to the current directory. If ENABLE_TESTING has not been run, -this command does nothing. The tests are run by the testing subsystem -by executing Exename with the specified arguments. Exename can be -either an executable built by this project or an arbitrary executable -on the system (like tclsh). The test will be run with the current -working directory set to the CMakeList.txt files corresponding -directory in the binary tree. Tests added using this signature do not -support generator expressions. +Add a test called ``<name>``. The test name may not contain spaces, +quotes, or other characters special in CMake syntax. The options are: +``COMMAND`` + Specify the test command-line. If ``<command>`` specifies an + executable target (created by :command:`add_executable`) it will + automatically be replaced by the location of the executable created + at build time. +``CONFIGURATIONS`` + Restrict execution of the test only to the named configurations. -:: - - add_test(NAME <name> [CONFIGURATIONS [Debug|Release|...]] - [WORKING_DIRECTORY dir] - COMMAND <command> [arg1 [arg2 ...]]) - -Add a test called <name>. The test name may not contain spaces, -quotes, or other characters special in CMake syntax. If COMMAND -specifies an executable target (created by add_executable) it will -automatically be replaced by the location of the executable created at -build time. If a CONFIGURATIONS option is given then the test will be -executed only when testing under one of the named configurations. If -a WORKING_DIRECTORY option is given then the test will be executed in -the given directory. - -Arguments after COMMAND may use "generator expressions" with the syntax -``$<...>``. See the :manual:`cmake-generator-expressions(7)` manual for -available expressions. +``WORKING_DIRECTORY`` + Set the :prop_test:`WORKING_DIRECTORY` test property to + specify the working directory in which to execute the test. + If not specified the test will be run with the current working + directory set to the build directory corresponding to the + current source directory. -Note that tgt is not added as a dependency of the target this -expression is evaluated on. +The ``COMMAND`` and ``WORKING_DIRECTORY`` options may use "generator +expressions" with the syntax ``$<...>``. See the +:manual:`cmake-generator-expressions(7)` manual for available expressions. -:: - - $<TARGET_POLICY:pol> = '1' if the policy was NEW when the 'head' target was created, else '0'. If the policy was not set, the warning message for the policy will be emitted. This generator expression only works for a subset of policies. - $<INSTALL_PREFIX> = Content of the install prefix when the target is exported via INSTALL(EXPORT) and empty otherwise. +Example usage:: -Boolean expressions: + add_test(NAME mytest + COMMAND testDriver --config $<CONFIGURATION> + --exe $<TARGET_FILE:myexe>) -:: +This creates a test ``mytest`` whose command runs a ``testDriver`` tool +passing the configuration name and the full path to the executable +file produced by target ``myexe``. - $<AND:?[,?]...> = '1' if all '?' are '1', else '0' - $<OR:?[,?]...> = '0' if all '?' are '0', else '1' - $<NOT:?> = '0' if '?' is '1', else '1' +.. note:: -where '?' is always either '0' or '1'. + CMake will generate tests only if the :command:`enable_testing` + command has been invoked. The :module:`CTest` module invokes the + command automatically when the ``BUILD_TESTING`` option is ``ON``. -Example usage: +--------------------------------------------------------------------- :: - add_test(NAME mytest - COMMAND testDriver --config $<CONFIGURATION> - --exe $<TARGET_FILE:myexe>) + add_test(<name> <command> [<arg>...]) -This creates a test "mytest" whose command runs a testDriver tool -passing the configuration name and the full path to the executable -file produced by target "myexe". +Add a test called ``<name>`` with the given command-line. Unlike +the above ``NAME`` signature no transformation is performed on the +command-line to support target names or generator expressions. diff --git a/Help/command/install.rst b/Help/command/install.rst index a463a60..47108f0 100644 --- a/Help/command/install.rst +++ b/Help/command/install.rst @@ -9,43 +9,50 @@ executed in order during installation. The order across directories is not defined. There are multiple signatures for this command. Some of them define -installation properties for files and targets. Properties common to +installation options for files and targets. Options common to multiple signatures are covered here but they are valid only for -signatures that specify them. - -DESTINATION arguments specify the directory on disk to which a file -will be installed. If a full path (with a leading slash or drive -letter) is given it is used directly. If a relative path is given it -is interpreted relative to the value of CMAKE_INSTALL_PREFIX. The -prefix can be relocated at install time using DESTDIR mechanism -explained in the CMAKE_INSTALL_PREFIX variable documentation. - -PERMISSIONS arguments specify permissions for installed files. Valid -permissions are OWNER_READ, OWNER_WRITE, OWNER_EXECUTE, GROUP_READ, -GROUP_WRITE, GROUP_EXECUTE, WORLD_READ, WORLD_WRITE, WORLD_EXECUTE, -SETUID, and SETGID. Permissions that do not make sense on certain -platforms are ignored on those platforms. - -The CONFIGURATIONS argument specifies a list of build configurations -for which the install rule applies (Debug, Release, etc.). - -The COMPONENT argument specifies an installation component name with -which the install rule is associated, such as "runtime" or -"development". During component-specific installation only install -rules associated with the given component name will be executed. -During a full installation all components are installed. If COMPONENT -is not provided a default component "Unspecified" is created. The -default component name may be controlled with the -CMAKE_INSTALL_DEFAULT_COMPONENT_NAME variable. - -The RENAME argument specifies a name for an installed file that may be -different from the original file. Renaming is allowed only when a -single file is installed by the command. - -The OPTIONAL argument specifies that it is not an error if the file to -be installed does not exist. - -The TARGETS signature: +signatures that specify them. The common options are: + +``DESTINATION`` + Specify the directory on disk to which a file will be installed. + If a full path (with a leading slash or drive letter) is given + it is used directly. If a relative path is given it is interpreted + relative to the value of the :variable:`CMAKE_INSTALL_PREFIX` variable. + The prefix can be relocated at install time using the ``DESTDIR`` + mechanism explained in the :variable:`CMAKE_INSTALL_PREFIX` variable + documentation. + +``PERMISSIONS`` + Specify permissions for installed files. Valid permissions are + ``OWNER_READ``, ``OWNER_WRITE``, ``OWNER_EXECUTE``, ``GROUP_READ``, + ``GROUP_WRITE``, ``GROUP_EXECUTE``, ``WORLD_READ``, ``WORLD_WRITE``, + ``WORLD_EXECUTE``, ``SETUID``, and ``SETGID``. Permissions that do + not make sense on certain platforms are ignored on those platforms. + +``CONFIGURATIONS`` + Specify a list of build configurations for which the install rule + applies (Debug, Release, etc.). + +``COMPONENT`` + Specify an installation component name with which the install rule + is associated, such as "runtime" or "development". During + component-specific installation only install rules associated with + the given component name will be executed. During a full installation + all components are installed. If ``COMPONENT`` is not provided a + default component "Unspecified" is created. The default component + name may be controlled with the + :variable:`CMAKE_INSTALL_DEFAULT_COMPONENT_NAME` variable. + +``RENAME`` + Specify a name for an installed file that may be different from the + original file. Renaming is allowed only when a single file is + installed by the command. + +``OPTIONAL`` + Specify that it is not an error if the file to be installed does + not exist. + +------------------------------------------------------------------------------ :: @@ -60,118 +67,115 @@ The TARGETS signature: [OPTIONAL] [NAMELINK_ONLY|NAMELINK_SKIP] ] [...]) -The TARGETS form specifies rules for installing targets from a +The ``TARGETS`` form specifies rules for installing targets from a project. There are five kinds of target files that may be installed: -ARCHIVE, LIBRARY, RUNTIME, FRAMEWORK, and BUNDLE. Executables are -treated as RUNTIME targets, except that those marked with the -MACOSX_BUNDLE property are treated as BUNDLE targets on OS X. Static -libraries are always treated as ARCHIVE targets. Module libraries are -always treated as LIBRARY targets. For non-DLL platforms shared -libraries are treated as LIBRARY targets, except that those marked -with the FRAMEWORK property are treated as FRAMEWORK targets on OS X. -For DLL platforms the DLL part of a shared library is treated as a -RUNTIME target and the corresponding import library is treated as an -ARCHIVE target. All Windows-based systems including Cygwin are DLL -platforms. The ARCHIVE, LIBRARY, RUNTIME, and FRAMEWORK arguments +``ARCHIVE``, ``LIBRARY``, ``RUNTIME``, ``FRAMEWORK``, and ``BUNDLE``. +Executables are treated as ``RUNTIME`` targets, except that those +marked with the ``MACOSX_BUNDLE`` property are treated as ``BUNDLE`` +targets on OS X. Static libraries are always treated as ``ARCHIVE`` +targets. Module libraries are always treated as ``LIBRARY`` targets. +For non-DLL platforms shared libraries are treated as ``LIBRARY`` +targets, except that those marked with the ``FRAMEWORK`` property are +treated as ``FRAMEWORK`` targets on OS X. For DLL platforms the DLL +part of a shared library is treated as a ``RUNTIME`` target and the +corresponding import library is treated as an ``ARCHIVE`` target. +All Windows-based systems including Cygwin are DLL platforms. +The ``ARCHIVE``, ``LIBRARY``, ``RUNTIME``, and ``FRAMEWORK`` arguments change the type of target to which the subsequent properties apply. If none is given the installation properties apply to all target types. If only one is given then only targets of that type will be installed (which can be used to install just a DLL or just an import -library).The INCLUDES DESTINATION specifies a list of directories -which will be added to the INTERFACE_INCLUDE_DIRECTORIES of the -<targets> when exported by install(EXPORT). If a relative path is -specified, it is treated as relative to the $<INSTALL_PREFIX>. - -The PRIVATE_HEADER, PUBLIC_HEADER, and RESOURCE arguments cause -subsequent properties to be applied to installing a FRAMEWORK shared -library target's associated files on non-Apple platforms. Rules +library). The ``INCLUDES DESTINATION`` specifies a list of directories +which will be added to the :prop_tgt:`INTERFACE_INCLUDE_DIRECTORIES` +target property of the ``<targets>`` when exported by the +:command:`install(EXPORT)` command. If a relative path is +specified, it is treated as relative to the ``$<INSTALL_PREFIX>``. + +The ``PRIVATE_HEADER``, ``PUBLIC_HEADER``, and ``RESOURCE`` arguments +cause subsequent properties to be applied to installing a ``FRAMEWORK`` +shared library target's associated files on non-Apple platforms. Rules defined by these arguments are ignored on Apple platforms because the associated files are installed into the appropriate locations inside -the framework folder. See documentation of the PRIVATE_HEADER, -PUBLIC_HEADER, and RESOURCE target properties for details. +the framework folder. See documentation of the +:prop_tgt:`PRIVATE_HEADER`, :prop_tgt:`PUBLIC_HEADER`, and +:prop_tgt:`RESOURCE` target properties for details. -Either NAMELINK_ONLY or NAMELINK_SKIP may be specified as a LIBRARY -option. On some platforms a versioned shared library has a symbolic -link such as - -:: +Either ``NAMELINK_ONLY`` or ``NAMELINK_SKIP`` may be specified as a +``LIBRARY`` option. On some platforms a versioned shared library +has a symbolic link such as:: lib<name>.so -> lib<name>.so.1 -where "lib<name>.so.1" is the soname of the library and "lib<name>.so" +where ``lib<name>.so.1`` is the soname of the library and ``lib<name>.so`` is a "namelink" allowing linkers to find the library when given -"-l<name>". The NAMELINK_ONLY option causes installation of only the -namelink when a library target is installed. The NAMELINK_SKIP option +``-l<name>``. The ``NAMELINK_ONLY`` option causes installation of only the +namelink when a library target is installed. The ``NAMELINK_SKIP`` option causes installation of library files other than the namelink when a library target is installed. When neither option is given both portions are installed. On platforms where versioned shared libraries do not have namelinks or when a library is not versioned the -NAMELINK_SKIP option installs the library and the NAMELINK_ONLY option -installs nothing. See the VERSION and SOVERSION target properties for -details on creating versioned shared libraries. +``NAMELINK_SKIP`` option installs the library and the ``NAMELINK_ONLY`` +option installs nothing. See the :prop_tgt:`VERSION` and +:prop_tgt:`SOVERSION` target properties for details on creating versioned +shared libraries. One or more groups of properties may be specified in a single call to -the TARGETS form of this command. A target may be installed more than -once to different locations. Consider hypothetical targets "myExe", -"mySharedLib", and "myStaticLib". The code +the ``TARGETS`` form of this command. A target may be installed more than +once to different locations. Consider hypothetical targets ``myExe``, +``mySharedLib``, and ``myStaticLib``. The code: -:: +.. code-block:: cmake - install(TARGETS myExe mySharedLib myStaticLib - RUNTIME DESTINATION bin - LIBRARY DESTINATION lib - ARCHIVE DESTINATION lib/static) - install(TARGETS mySharedLib DESTINATION /some/full/path) + install(TARGETS myExe mySharedLib myStaticLib + RUNTIME DESTINATION bin + LIBRARY DESTINATION lib + ARCHIVE DESTINATION lib/static) + install(TARGETS mySharedLib DESTINATION /some/full/path) -will install myExe to <prefix>/bin and myStaticLib to -<prefix>/lib/static. On non-DLL platforms mySharedLib will be -installed to <prefix>/lib and /some/full/path. On DLL platforms the -mySharedLib DLL will be installed to <prefix>/bin and /some/full/path -and its import library will be installed to <prefix>/lib/static and -/some/full/path. +will install ``myExe`` to ``<prefix>/bin`` and ``myStaticLib`` to +``<prefix>/lib/static``. On non-DLL platforms ``mySharedLib`` will be +installed to ``<prefix>/lib`` and ``/some/full/path``. On DLL platforms +the ``mySharedLib`` DLL will be installed to ``<prefix>/bin`` and +``/some/full/path`` and its import library will be installed to +``<prefix>/lib/static`` and ``/some/full/path``. -The EXPORT option associates the installed target files with an export -called <export-name>. It must appear before any RUNTIME, LIBRARY, or -ARCHIVE options. To actually install the export file itself, call -install(EXPORT). See documentation of the install(EXPORT ...) -signature below for details. +The ``EXPORT`` option associates the installed target files with an +export called ``<export-name>``. It must appear before any ``RUNTIME``, +``LIBRARY``, or ``ARCHIVE`` options. To actually install the export +file itself, call ``install(EXPORT)``, documented below. -Installing a target with EXCLUDE_FROM_ALL set to true has undefined -behavior. +Installing a target with the :prop_tgt:`EXCLUDE_FROM_ALL` target property +set to ``TRUE`` has undefined behavior. -The FILES signature: +------------------------------------------------------------------------------ :: - install(FILES files... DESTINATION <dir> + install(<FILES|PROGRAMS> files... DESTINATION <dir> [PERMISSIONS permissions...] [CONFIGURATIONS [Debug|Release|...]] [COMPONENT <component>] [RENAME <name>] [OPTIONAL]) -The FILES form specifies rules for installing files for a project. +The ``FILES`` form specifies rules for installing files for a project. File names given as relative paths are interpreted with respect to the current source directory. Files installed by this form are by default -given permissions OWNER_WRITE, OWNER_READ, GROUP_READ, and WORLD_READ -if no PERMISSIONS argument is given. - -The PROGRAMS signature: - -:: - - install(PROGRAMS files... DESTINATION <dir> - [PERMISSIONS permissions...] - [CONFIGURATIONS [Debug|Release|...]] - [COMPONENT <component>] - [RENAME <name>] [OPTIONAL]) +given permissions ``OWNER_WRITE``, ``OWNER_READ``, ``GROUP_READ``, and +``WORLD_READ`` if no ``PERMISSIONS`` argument is given. -The PROGRAMS form is identical to the FILES form except that the -default permissions for the installed file also include OWNER_EXECUTE, -GROUP_EXECUTE, and WORLD_EXECUTE. This form is intended to install -programs that are not targets, such as shell scripts. Use the TARGETS +The ``PROGRAMS`` form is identical to the ``FILES`` form except that the +default permissions for the installed file also include ``OWNER_EXECUTE``, +``GROUP_EXECUTE``, and ``WORLD_EXECUTE``. This form is intended to install +programs that are not targets, such as shell scripts. Use the ``TARGETS`` form to install targets built within the project. -The DIRECTORY signature: +The list of ``files...`` given to ``FILES`` or ``PROGRAMS`` may use +"generator expressions" with the syntax ``$<...>``. See the +:manual:`cmake-generator-expressions(7)` manual for available expressions. +However, if any item begins in a generator expression it must evaluate +to a full path. + +------------------------------------------------------------------------------ :: @@ -184,7 +188,7 @@ The DIRECTORY signature: [[PATTERN <pattern> | REGEX <regex>] [EXCLUDE] [PERMISSIONS permissions...]] [...]) -The DIRECTORY form installs contents of one or more directories to a +The ``DIRECTORY`` form installs contents of one or more directories to a given destination. The directory structure is copied verbatim to the destination. The last component of each directory name is appended to the destination directory but a trailing slash may be used to avoid @@ -192,45 +196,45 @@ this because it leaves the last component empty. Directory names given as relative paths are interpreted with respect to the current source directory. If no input directory names are given the destination directory will be created but nothing will be installed -into it. The FILE_PERMISSIONS and DIRECTORY_PERMISSIONS options +into it. The ``FILE_PERMISSIONS`` and ``DIRECTORY_PERMISSIONS`` options specify permissions given to files and directories in the destination. -If USE_SOURCE_PERMISSIONS is specified and FILE_PERMISSIONS is not, +If ``USE_SOURCE_PERMISSIONS`` is specified and ``FILE_PERMISSIONS`` is not, file permissions will be copied from the source directory structure. If no permissions are specified files will be given the default -permissions specified in the FILES form of the command, and the +permissions specified in the ``FILES`` form of the command, and the directories will be given the default permissions specified in the -PROGRAMS form of the command. +``PROGRAMS`` form of the command. Installation of directories may be controlled with fine granularity -using the PATTERN or REGEX options. These "match" options specify a +using the ``PATTERN`` or ``REGEX`` options. These "match" options specify a globbing pattern or regular expression to match directories or files encountered within input directories. They may be used to apply certain options (see below) to a subset of the files and directories encountered. The full path to each input file or directory (with -forward slashes) is matched against the expression. A PATTERN will +forward slashes) is matched against the expression. A ``PATTERN`` will match only complete file names: the portion of the full path matching the pattern must occur at the end of the file name and be preceded by -a slash. A REGEX will match any portion of the full path but it may -use '/' and '$' to simulate the PATTERN behavior. By default all +a slash. A ``REGEX`` will match any portion of the full path but it may +use ``/`` and ``$`` to simulate the ``PATTERN`` behavior. By default all files and directories are installed whether or not they are matched. -The FILES_MATCHING option may be given before the first match option +The ``FILES_MATCHING`` option may be given before the first match option to disable installation of files (but not directories) not matched by any expression. For example, the code -:: +.. code-block:: cmake install(DIRECTORY src/ DESTINATION include/myproj FILES_MATCHING PATTERN "*.h") will extract and install header files from a source tree. -Some options may follow a PATTERN or REGEX expression and are applied -only to files or directories matching them. The EXCLUDE option will -skip the matched file or directory. The PERMISSIONS option overrides +Some options may follow a ``PATTERN`` or ``REGEX`` expression and are applied +only to files or directories matching them. The ``EXCLUDE`` option will +skip the matched file or directory. The ``PERMISSIONS`` option overrides the permissions setting for the matched file or directory. For example the code -:: +.. code-block:: cmake install(DIRECTORY icons scripts/ DESTINATION share/myproj PATTERN "CVS" EXCLUDE @@ -238,31 +242,31 @@ example the code PERMISSIONS OWNER_EXECUTE OWNER_WRITE OWNER_READ GROUP_EXECUTE GROUP_READ) -will install the icons directory to share/myproj/icons and the scripts -directory to share/myproj. The icons will get default file -permissions, the scripts will be given specific permissions, and any -CVS directories will be excluded. +will install the ``icons`` directory to ``share/myproj/icons`` and the +``scripts`` directory to ``share/myproj``. The icons will get default +file permissions, the scripts will be given specific permissions, and any +``CVS`` directories will be excluded. -The SCRIPT and CODE signature: +------------------------------------------------------------------------------ :: install([[SCRIPT <file>] [CODE <code>]] [...]) -The SCRIPT form will invoke the given CMake script files during +The ``SCRIPT`` form will invoke the given CMake script files during installation. If the script file name is a relative path it will be -interpreted with respect to the current source directory. The CODE +interpreted with respect to the current source directory. The ``CODE`` form will invoke the given CMake code during installation. Code is specified as a single argument inside a double-quoted string. For example, the code -:: +.. code-block:: cmake install(CODE "MESSAGE(\"Sample install message.\")") will print a message during installation. -The EXPORT signature: +------------------------------------------------------------------------------ :: @@ -273,44 +277,47 @@ The EXPORT signature: [EXPORT_LINK_INTERFACE_LIBRARIES] [COMPONENT <component>]) -The EXPORT form generates and installs a CMake file containing code to +The ``EXPORT`` form generates and installs a CMake file containing code to import targets from the installation tree into another project. -Target installations are associated with the export <export-name> -using the EXPORT option of the install(TARGETS ...) signature -documented above. The NAMESPACE option will prepend <namespace> to +Target installations are associated with the export ``<export-name>`` +using the ``EXPORT`` option of the ``install(TARGETS)`` signature +documented above. The ``NAMESPACE`` option will prepend ``<namespace>`` to the target names as they are written to the import file. By default -the generated file will be called <export-name>.cmake but the FILE +the generated file will be called ``<export-name>.cmake`` but the ``FILE`` option may be used to specify a different name. The value given to -the FILE option must be a file name with the ".cmake" extension. If a -CONFIGURATIONS option is given then the file will only be installed +the ``FILE`` option must be a file name with the ``.cmake`` extension. +If a ``CONFIGURATIONS`` option is given then the file will only be installed when one of the named configurations is installed. Additionally, the generated import file will reference only the matching target -configurations. The EXPORT_LINK_INTERFACE_LIBRARIES keyword, if +configurations. The ``EXPORT_LINK_INTERFACE_LIBRARIES`` keyword, if present, causes the contents of the properties matching ``(IMPORTED_)?LINK_INTERFACE_LIBRARIES(_<CONFIG>)?`` to be exported, when -policy CMP0022 is NEW. If a COMPONENT option is specified that does -not match that given to the targets associated with <export-name> the -behavior is undefined. If a library target is included in the export -but a target to which it links is not included the behavior is -unspecified. +policy :policy:`CMP0022` is ``NEW``. If a ``COMPONENT`` option is +specified that does not match that given to the targets associated with +``<export-name>`` the behavior is undefined. If a library target is +included in the export but a target to which it links is not included +the behavior is unspecified. -The EXPORT form is useful to help outside projects use targets built +The ``EXPORT`` form is useful to help outside projects use targets built and installed by the current project. For example, the code -:: +.. code-block:: cmake install(TARGETS myexe EXPORT myproj DESTINATION bin) install(EXPORT myproj NAMESPACE mp_ DESTINATION lib/myproj) -will install the executable myexe to <prefix>/bin and code to import -it in the file "<prefix>/lib/myproj/myproj.cmake". An outside project -may load this file with the include command and reference the myexe +will install the executable myexe to ``<prefix>/bin`` and code to import +it in the file ``<prefix>/lib/myproj/myproj.cmake``. An outside project +may load this file with the include command and reference the ``myexe`` executable from the installation tree using the imported target name -mp_myexe as if the target were built in its own tree. - -NOTE: This command supercedes the INSTALL_TARGETS command and the -target properties PRE_INSTALL_SCRIPT and POST_INSTALL_SCRIPT. It also -replaces the FILES forms of the INSTALL_FILES and INSTALL_PROGRAMS -commands. The processing order of these install rules relative to -those generated by INSTALL_TARGETS, INSTALL_FILES, and -INSTALL_PROGRAMS commands is not defined. +``mp_myexe`` as if the target were built in its own tree. + +.. note:: + This command supercedes the :command:`install_targets` command and + the :prop_tgt:`PRE_INSTALL_SCRIPT` and :prop_tgt:`POST_INSTALL_SCRIPT` + target properties. It also replaces the ``FILES`` forms of the + :command:`install_files` and :command:`install_programs` commands. + The processing order of these install rules relative to + those generated by :command:`install_targets`, + :command:`install_files`, and :command:`install_programs` commands + is not defined. diff --git a/Help/manual/cmake-buildsystem.7.rst b/Help/manual/cmake-buildsystem.7.rst index d252473..501b924 100644 --- a/Help/manual/cmake-buildsystem.7.rst +++ b/Help/manual/cmake-buildsystem.7.rst @@ -820,6 +820,16 @@ This way, the build specification of ``exe1`` is expressed entirely as linked targets, and the complexity of compiler-specific flags is encapsulated in an ``INTERFACE`` library target. +The properties permitted to be set on or read from an ``INTERFACE`` library +are: + +* Properties matching ``INTERFACE_*`` +* Built-in properties matching ``COMPATIBLE_INTERFACE_*`` +* ``EXPORT_NAME`` +* ``IMPORTED`` +* ``NAME`` +* Properties matching ``MAP_IMPORTED_CONFIG_*`` + ``INTERFACE`` libraries may be installed and exported. Any content they refer to must be installed separately: diff --git a/Help/policy/CMP0043.rst b/Help/policy/CMP0043.rst index 43d6df2..629e502 100644 --- a/Help/policy/CMP0043.rst +++ b/Help/policy/CMP0043.rst @@ -18,16 +18,22 @@ or via :command:`target_compile_definitions`: .. code-block:: cmake - # Old Interface: + # Old Interfaces: set_property(TARGET tgt APPEND PROPERTY COMPILE_DEFINITIONS_DEBUG DEBUG_MODE ) + set_property(DIRECTORY APPEND PROPERTY + COMPILE_DEFINITIONS_DEBUG DIR_DEBUG_MODE + ) # New Interfaces: set_property(TARGET tgt APPEND PROPERTY COMPILE_DEFINITIONS $<$<CONFIG:Debug>:DEBUG_MODE> ) target_compile_definitions(tgt PRIVATE $<$<CONFIG:Debug>:DEBUG_MODE>) + set_property(DIRECTORY APPEND PROPERTY + COMPILE_DEFINITIONS $<$<CONFIG:Debug>:DIR_DEBUG_MODE> + ) The OLD behavior for this policy is to consume the content of the suffixed :prop_tgt:`COMPILE_DEFINITIONS_<CONFIG>` target property when generating the diff --git a/Help/release/3.0.rst b/Help/release/3.0.0.rst index 45f7635..e92c293 100644 --- a/Help/release/3.0.rst +++ b/Help/release/3.0.0.rst @@ -1,5 +1,5 @@ -CMake 3.0 Release Notes -*********************** +CMake 3.0.0 Release Notes +************************* .. only:: html @@ -39,7 +39,7 @@ Documentation Changes - :manual:`cmake-toolchains(7)` - :manual:`cmake-variables(7)`, replacing ``cmakevars(1)`` -* Release notes for CMake 3.0 and above will now be included with +* Release notes for CMake 3.0.0 and above will now be included with the html documentation. New Features @@ -102,6 +102,10 @@ Commands configuration because it will not be available. Use :ref:`Alias Targets` instead. See policy :policy:`CMP0024`. +* The :command:`install(FILES)` command learned to support + :manual:`generator expressions <cmake-generator-expressions(7)>` + in the list of files. + * The :command:`project` command learned to set some version variables to values specified by the new ``VERSION`` option or to empty strings. See policy :policy:`CMP0048`. @@ -216,6 +220,9 @@ Modules * A new :module:`FindLua` module has been added to support :command:`find_package(Lua)` calls. +* The :module:`FindBoost` module learned a new ``Boost_NAMESPACE`` + option to change the ``boost`` prefix on library names. + * The :module:`FindBoost` module learned to control search for libraies with the ``g`` tag (for MS debug runtime) with a new ``Boost_USE_DEBUG_RUNTIME`` option. It is ``ON`` by @@ -238,6 +245,8 @@ Modules for Qt executables. This helps disambiguate when using multiple :manual:`Qt versions <cmake-qt(7)>` in the same buildsystem. +* The :module:`FindRuby` module learned to search for Ruby 2.0 and 2.1. + Generator Expressions --------------------- @@ -387,6 +396,11 @@ Deprecated and Removed Features Other Changes ============= +* The version scheme was changed to use only two components for + the feature level instead of three. The third component will + now be used for bug-fix releases or the date of development versions. + See the :variable:`CMAKE_VERSION` variable documentation for details. + * The default install locations of CMake itself on Windows and OS X no longer contain the CMake version number. This allows for easy replacement without re-generating local build trees diff --git a/Help/release/dev/0-sample-topic.rst b/Help/release/dev/0-sample-topic.rst deleted file mode 100644 index e4cc01e..0000000 --- a/Help/release/dev/0-sample-topic.rst +++ /dev/null @@ -1,7 +0,0 @@ -0-sample-topic --------------- - -* This is a sample release note for the change in a topic. - Developers should add similar notes for each topic branch - making a noteworthy change. Each document should be named - and titled to match the topic name to avoid merge conflicts. diff --git a/Help/release/dev/Boost_NAMESPACE.rst b/Help/release/dev/Boost_NAMESPACE.rst deleted file mode 100644 index 434db29..0000000 --- a/Help/release/dev/Boost_NAMESPACE.rst +++ /dev/null @@ -1,5 +0,0 @@ -Boost_NAMESPACE ---------------- - -* The :module:`FindBoost` module learned a new ``Boost_NAMESPACE`` - option to change the ``boost`` prefix on library names. diff --git a/Help/release/index.rst b/Help/release/index.rst index 5c3a771..752c568 100644 --- a/Help/release/index.rst +++ b/Help/release/index.rst @@ -5,12 +5,10 @@ CMake Release Notes This file should include the adjacent "dev.txt" file in development versions but not in release versions. -.. include:: dev.txt - Releases ======== .. toctree:: :maxdepth: 1 - 3.0 <3.0> + 3.0.0 <3.0.0> diff --git a/Help/variable/CMAKE_TWEAK_VERSION.rst b/Help/variable/CMAKE_TWEAK_VERSION.rst index a2c8f35..be2e050 100644 --- a/Help/variable/CMAKE_TWEAK_VERSION.rst +++ b/Help/variable/CMAKE_TWEAK_VERSION.rst @@ -1,5 +1,11 @@ CMAKE_TWEAK_VERSION ------------------- -Fourth version number component of the :variable:`CMAKE_VERSION` -variable. +Defined to ``0`` for compatibility with code written for older +CMake versions that may have defined higher values. + +.. note:: + + In CMake versions 2.8.2 through 2.8.12, this variable holds + the fourth version number component of the + :variable:`CMAKE_VERSION` variable. diff --git a/Help/variable/CMAKE_VERSION.rst b/Help/variable/CMAKE_VERSION.rst index 6184f08..bbb1d91 100644 --- a/Help/variable/CMAKE_VERSION.rst +++ b/Help/variable/CMAKE_VERSION.rst @@ -1,24 +1,23 @@ CMAKE_VERSION ------------- -The CMake version string as up to four non-negative integer components +The CMake version string as three non-negative integer components separated by ``.`` and possibly followed by ``-`` and other information. -The first three components represent the feature level and the fourth +The first two components represent the feature level and the third component represents either a bug-fix level or development date. Release versions and release candidate versions of CMake use the format:: - <major>.<minor>.<patch>[.<tweak>][-rc<n>] + <major>.<minor>.<patch>[-rc<n>] -where the ``<tweak>`` component is less than ``20000000``. Development +where the ``<patch>`` component is less than ``20000000``. Development versions of CMake use the format:: - <major>.<minor>.<patch>.<date>[-<id>] + <major>.<minor>.<date>[-<id>] where the ``<date>`` component is of format ``CCYYMMDD`` and ``<id>`` may contain arbitrary text. This represents development as of a -particular date following the ``<major>.<minor>.<patch>`` feature -release. +particular date following the ``<major>.<minor>`` feature release. Individual component values are also available in variables: @@ -35,6 +34,12 @@ strings as floating-point numbers. .. note:: + CMake versions 2.8.2 through 2.8.12 used three components for the + feature level. Release versions represented the bug-fix level in a + fourth component, i.e. ``<major>.<minor>.<patch>[.<tweak>][-rc<n>]``. + Development versions represented the development date in the fourth + component, i.e. ``<major>.<minor>.<patch>.<date>[-<id>]``. + CMake versions prior to 2.8.2 used three components for the feature level and had no bug-fix component. Release versions used an even-valued second component, i.e. |