https://github.com/Kitware/CMake
Revision ffb9978e95ecab961f90be39e9a1225fdf6c0ae3 authored by Brad King on 16 September 2021, 12:23:17 UTC, committed by Kitware Robot on 16 September 2021, 12:24:56 UTC
1230ceb97e Help: Improve explanation on CMAKE_POLICY_WARNING warnings occur

Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !6522
2 parent s f5445e3 + 1230ceb
Raw File
Tip revision: ffb9978e95ecab961f90be39e9a1225fdf6c0ae3 authored by Brad King on 16 September 2021, 12:23:17 UTC
Merge topic 'clarify_cmake_policy_warning_doc'
Tip revision: ffb9978
CMP0084.rst
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`.

This policy was introduced in CMake version 3.14.  CMake version
|release| warns when the policy is not set and uses ``OLD`` behavior.
Use the :command:`cmake_policy` command to set it to ``OLD`` or ``NEW``
explicitly.

.. include:: DEPRECATED.txt
back to top