mirror of
https://github.com/Detanup01/gbe_fork.git
synced 2024-12-03 07:45:37 +08:00
27 lines
1.2 KiB
ReStructuredText
27 lines
1.2 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.
|
||
|
|
|
||
|
|
This policy was introduced in CMake version 3.24. Use the
|
||
|
|
:command:`cmake_policy` command to set it to ``OLD`` or ``NEW`` explicitly.
|
||
|
|
Unlike many policies, CMake version |release| does *not* warn
|
||
|
|
when this policy is not set and simply uses ``OLD`` behavior.
|
||
|
|
|
||
|
|
.. include:: DEPRECATED.txt
|