mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-05 13:20:47 -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.
29 lines
1.2 KiB
ReStructuredText
29 lines
1.2 KiB
ReStructuredText
CMP0090
|
|
-------
|
|
|
|
.. versionadded:: 3.15
|
|
|
|
:command:`export(PACKAGE)` does not populate package registry by default.
|
|
|
|
In CMake 3.14 and below the :command:`export(PACKAGE)` command populated the
|
|
user package registry by default and users needed to set the
|
|
:variable:`CMAKE_EXPORT_NO_PACKAGE_REGISTRY` to disable it, e.g. in automated
|
|
build and packaging environments. Since the user package registry is stored
|
|
outside the build tree, this side effect should not be enabled by default.
|
|
Therefore CMake 3.15 and above prefer that :command:`export(PACKAGE)` does
|
|
nothing unless an explicit :variable:`CMAKE_EXPORT_PACKAGE_REGISTRY` variable
|
|
is set to enable it. This policy provides compatibility with projects that
|
|
have not been updated.
|
|
|
|
The ``OLD`` behavior for this policy is for :command:`export(PACKAGE)` command
|
|
to populate the user package registry unless
|
|
:variable:`CMAKE_EXPORT_NO_PACKAGE_REGISTRY` is enabled.
|
|
The ``NEW`` behavior is for :command:`export(PACKAGE)` command to do nothing
|
|
unless the :variable:`CMAKE_EXPORT_PACKAGE_REGISTRY` is enabled.
|
|
|
|
.. |INTRODUCED_IN_CMAKE_VERSION| replace:: 3.15
|
|
.. |WARNS_OR_DOES_NOT_WARN| replace:: does *not* warn
|
|
.. include:: STANDARD_ADVICE.txt
|
|
|
|
.. include:: DEPRECATED.txt
|