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.
28 lines
1.1 KiB
ReStructuredText
28 lines
1.1 KiB
ReStructuredText
CMP0155
|
|
-------
|
|
|
|
.. versionadded:: 3.28
|
|
|
|
C++ sources in targets with at least C++20 are scanned for imports
|
|
when supported.
|
|
|
|
CMake 3.27 and below assume that C++ sources do not ``import`` modules.
|
|
CMake 3.28 and above prefer to assume that C++ sources in targets using C++20
|
|
or higher might ``import`` modules, and must be scanned before compiling,
|
|
unless explicitly disabled. This policy provides compatibility for projects
|
|
that use C++20 or higher, without modules, that have not been updated to turn
|
|
off scanning, e.g., via the :variable:`CMAKE_CXX_SCAN_FOR_MODULES` variable.
|
|
See the :manual:`cmake-cxxmodules(7)` manual for more details on C++ module
|
|
support.
|
|
|
|
The ``OLD`` behavior for this policy is to assume that C++ 20 and newer
|
|
sources do not import modules. The ``NEW`` behavior for this policy is to
|
|
assume that C++ 20 and newer files may import modules if the compiler
|
|
understands how to scan for their dependencies, and need to be scanned.
|
|
|
|
.. |INTRODUCED_IN_CMAKE_VERSION| replace:: 3.28
|
|
.. |WARNS_OR_DOES_NOT_WARN| replace:: does *not* warn
|
|
.. include:: STANDARD_ADVICE.txt
|
|
|
|
.. include:: DEPRECATED.txt
|