mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-06 05:40:54 -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.0 KiB
ReStructuredText
28 lines
1.0 KiB
ReStructuredText
CMP0084
|
|
-------
|
|
|
|
.. versionadded:: 3.14
|
|
|
|
The :module:`FindQt` module does not exist for :command:`find_package`.
|
|
|
|
The existence of :module:`FindQt` means that for Qt upstream to provide
|
|
package config files that can be found by ``find_package(Qt)``, the consuming
|
|
project has to explicitly specify ``find_package(Qt CONFIG)``. Removing this
|
|
module gives Qt a path forward for exporting its own config files which can
|
|
easily be found by consuming projects.
|
|
|
|
This policy pretends that CMake's internal :module:`FindQt` module does not
|
|
exist for :command:`find_package`. If a project really wants to use Qt 3 or 4,
|
|
it can call ``find_package(Qt[34])``, ``include(FindQt)``, or add
|
|
:module:`FindQt` to their :variable:`CMAKE_MODULE_PATH`.
|
|
|
|
The ``OLD`` behavior of this policy is for :module:`FindQt` to exist for
|
|
:command:`find_package`. The ``NEW`` behavior is to pretend that it doesn't
|
|
exist for :command:`find_package`.
|
|
|
|
.. |INTRODUCED_IN_CMAKE_VERSION| replace:: 3.14
|
|
.. |WARNS_OR_DOES_NOT_WARN| replace:: warns
|
|
.. include:: STANDARD_ADVICE.txt
|
|
|
|
.. include:: DEPRECATED.txt
|