mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-05 21:31:08 -06:00
ad3c2c0b03
Every policy's documentation has a paragraph on what version of CMake introduced it, how to set the policy, and whether CMake warns if the policy is not set. The wording of this paragraph has diverged across policies over time. Factor the paragraph out into a standard advice document included by every policy.
27 lines
1.1 KiB
ReStructuredText
27 lines
1.1 KiB
ReStructuredText
CMP0005
|
|
-------
|
|
|
|
Preprocessor definition values are now escaped automatically.
|
|
|
|
This policy determines whether or not CMake should generate escaped
|
|
preprocessor definition values added via add_definitions. CMake
|
|
versions 2.4 and below assumed that only trivial values would be given
|
|
for macros in add_definitions calls. It did not attempt to escape
|
|
non-trivial values such as string literals in generated build rules.
|
|
CMake versions 2.6 and above support escaping of most values, but
|
|
cannot assume the user has not added escapes already in an attempt to
|
|
work around limitations in earlier versions.
|
|
|
|
The ``OLD`` behavior for this policy is to place definition values given
|
|
to add_definitions directly in the generated build rules without
|
|
attempting to escape anything. The ``NEW`` behavior for this policy is to
|
|
generate correct escapes for all native build tools automatically.
|
|
See documentation of the ``COMPILE_DEFINITIONS`` target property for
|
|
limitations of the escaping implementation.
|
|
|
|
.. |INTRODUCED_IN_CMAKE_VERSION| replace:: 2.6.0
|
|
.. |WARNS_OR_DOES_NOT_WARN| replace:: warns
|
|
.. include:: STANDARD_ADVICE.txt
|
|
|
|
.. include:: DEPRECATED.txt
|