Commit 5d05124c authored by Brad King's avatar Brad King Committed by Kitware Robot
Browse files

Merge topic 'doc-policy-version-3.0'

aab11bca Help: Change version 3.0.0 -> 3.0 in policy docs
parents 89d49ecc aab11bca
......@@ -17,6 +17,6 @@ The OLD behavior for this policy is to allow including the result of
an export() command. The NEW behavior for this policy is not to
allow including the result of an export() command.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -3,12 +3,12 @@ CMP0025
Compiler id for Apple Clang is now AppleClang.
CMake >= 3.0.0 recognize that Apple Clang is a different compiler
CMake >= 3.0 recognize that Apple Clang is a different compiler
than upstream Clang and that they have different version numbers.
CMake now prefers to present this to projects by setting
CMAKE_<LANG>_COMPILER_ID to "AppleClang" instead of "Clang". However,
existing projects may assume the compiler id for Apple Clang is just
"Clang" as it was in CMake < 3.0.0. Therefore this policy determines
"Clang" as it was in CMake < 3.0. Therefore this policy determines
for Apple Clang which compiler id to report in
CMAKE_<LANG>_COMPILER_ID after <LANG> is enabled by the project() or
enable_language() command.
......@@ -16,6 +16,6 @@ enable_language() command.
The OLD behavior for this policy is to use compiler id "Clang". The
NEW behavior for this policy is to use compiler id "AppleClang".
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -20,6 +20,6 @@ The OLD behavior for this policy is to allow reading the LOCATION
property from build-targets. The NEW behavior for this policy is to
not to allow reading the LOCATION property from build-targets.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -20,6 +20,6 @@ The NEW behavior of this policy is to report an error if an entry in
the INTERFACE_INCLUDE_DIRECTORIES of a generator-expression
conditionally linked IMPORTED target does not exist.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -18,6 +18,6 @@ even if the search term contains double-colons. The NEW behavior for this
policy is to issue a FATAL_ERROR if a link dependency contains
double-colons but is not an IMPORTED target or an ALIAS target.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -6,5 +6,5 @@ The :command:`subdir_depends` command should not be called.
The implementation of this command has been empty since December 2001
but was kept in CMake for compatibility for a long time.
.. |disallowed_version| replace:: 3.0.0
.. |disallowed_version| replace:: 3.0
.. include:: DISALLOWED_COMMAND.txt
......@@ -7,5 +7,5 @@ This command was created in September 2001 to support VTK before
modern CMake language and custom command capabilities. VTK has
not used it in years.
.. |disallowed_version| replace:: 3.0.0
.. |disallowed_version| replace:: 3.0
.. include:: DISALLOWED_COMMAND.txt
......@@ -9,5 +9,5 @@ not work when the toolchain in use does not match the ABI of
the CMake process. It has been mostly superseded by the
:command:`macro` and :command:`function` commands.
.. |disallowed_version| replace:: 3.0.0
.. |disallowed_version| replace:: 3.0
.. include:: DISALLOWED_COMMAND.txt
......@@ -9,5 +9,5 @@ has evolved since then but is not exposed through this command. The
scanning capabilities of this command are very limited and this
functionality is better achieved through dedicated outside tools.
.. |disallowed_version| replace:: 3.0.0
.. |disallowed_version| replace:: 3.0
.. include:: DISALLOWED_COMMAND.txt
......@@ -10,5 +10,5 @@ work for applications outside of the original build tree of a project.
The functionality has been superseded by the :command:`export` and
:command:`install(EXPORT)` commands.
.. |disallowed_version| replace:: 3.0.0
.. |disallowed_version| replace:: 3.0
.. include:: DISALLOWED_COMMAND.txt
......@@ -7,5 +7,5 @@ This command was introduced in March 2001 to help build executables used to
generate other files. This approach has long been replaced by
:command:`add_executable` combined with :command:`add_custom_command`.
.. |disallowed_version| replace:: 3.0.0
.. |disallowed_version| replace:: 3.0
.. include:: DISALLOWED_COMMAND.txt
......@@ -6,5 +6,5 @@ The :command:`variable_requires` command should not be called.
This command was introduced in November 2001 to perform some conditional
logic. It has long been replaced by the :command:`if` command.
.. |disallowed_version| replace:: 3.0.0
.. |disallowed_version| replace:: 3.0
.. include:: DISALLOWED_COMMAND.txt
......@@ -8,5 +8,5 @@ operating system and compiler combination. The command has long been
documented as discouraged and replaced by the :variable:`CMAKE_SYSTEM`
and :variable:`CMAKE_<LANG>_COMPILER` variables.
.. |disallowed_version| replace:: 3.0.0
.. |disallowed_version| replace:: 3.0
.. include:: DISALLOWED_COMMAND.txt
......@@ -21,6 +21,6 @@ reserved names or which do not match the validity pattern.
The NEW behavior for this policy is to report an error
if an add_* command is used with an invalid target name.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -11,6 +11,6 @@ The OLD behavior for this policy is to ignore targets which list themselves
in their own link implementation. The NEW behavior for this policy is to
report an error if a target attempts to link to itself.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -12,6 +12,6 @@ libraries of utility targets. The NEW behavior for this policy is to
report an error if an attempt is made to set the link libraries of a
utility target.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -11,6 +11,6 @@ The OLD behavior for this policy is to ignore custom commands
for unknown targets. The NEW behavior for this policy is to report an error
if the target referenced in :command:`add_custom_command` is unknown.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -20,6 +20,6 @@ contain a generator expression. The NEW behavior for this policy is to report
an error if a generator expression appears in another location and the path is
relative.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -9,11 +9,11 @@ name. This was enabled by setting the target property
flexible and powerful mechanism than ``@executable_path`` or ``@loader_path``
for locating shared libraries.
CMake 3.0.0 and later prefer this property to be ON by default. Projects
CMake 3.0 and later prefer this property to be ON by default. Projects
wanting ``@rpath`` in a target's install name may remove any setting of
the :prop_tgt:`INSTALL_NAME_DIR` and :variable:`CMAKE_INSTALL_NAME_DIR`
variables.
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
......@@ -34,6 +34,6 @@ The OLD behavior for this policy is to consume the content of the suffixed
compilation command. The NEW behavior for this policy is to ignore the content
of the :prop_tgt:`COMPILE_DEFINITIONS_<CONFIG>` target property .
This policy was introduced in CMake version 3.0.0. CMake version
This policy was introduced in CMake version 3.0. CMake version
|release| warns when the policy is not set and uses OLD behavior. Use
the cmake_policy command to set it to OLD or NEW explicitly.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment