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
Tip revision: ffb9978e95ecab961f90be39e9a1225fdf6c0ae3 authored by Brad King on 16 September 2021, 12:23:17 UTC
Merge topic 'clarify_cmake_policy_warning_doc'
Merge topic 'clarify_cmake_policy_warning_doc'
Tip revision: ffb9978
CMP0050.rst
CMP0050
-------
Disallow add_custom_command SOURCE signatures.
CMake 2.8.12 and lower allowed a signature for :command:`add_custom_command`
which specified an input to a command. This was undocumented behavior.
Modern use of CMake associates custom commands with their output, rather
than their input.
The ``OLD`` behavior for this policy is to allow the use of
:command:`add_custom_command` SOURCE signatures. The ``NEW`` behavior for this
policy is to issue an error if such a signature is used.
This policy was introduced in CMake version 3.0.
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
Computing file changes ...
