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.
26 lines
1.1 KiB
ReStructuredText
26 lines
1.1 KiB
ReStructuredText
CMP0132
|
|
-------
|
|
|
|
.. versionadded:: 3.24
|
|
|
|
Apart from when using the Xcode generator and some Visual Studio generators,
|
|
CMake 3.23 and below will set environment variables like :envvar:`CC`,
|
|
:envvar:`CXX`, etc. when the corresponding language is enabled.
|
|
This only occurs on the very first time CMake is run in a build directory,
|
|
and the environment variables are only defined at configure time, not build
|
|
time. On subsequent CMake runs, these environment variables are not set,
|
|
opening up the opportunity for different behavior between the first and
|
|
subsequent CMake runs. CMake 3.24 and above prefer to not set these
|
|
environment variables when a language is enabled, even on the first run in
|
|
a build directory.
|
|
|
|
The ``OLD`` behavior for this policy sets the relevant environment variable
|
|
on the first run when a language is enabled. The ``NEW`` behavior for this
|
|
policy does not set any such environment variables.
|
|
|
|
.. |INTRODUCED_IN_CMAKE_VERSION| replace:: 3.24
|
|
.. |WARNS_OR_DOES_NOT_WARN| replace:: does *not* warn
|
|
.. include:: STANDARD_ADVICE.txt
|
|
|
|
.. include:: DEPRECATED.txt
|