482a3bf3f0
The most likely documentation page a project author will read in response to a policy warning is the page for the policy itself. Add to every policy documentation page a note explicitly stating that the OLD behavior is deprecated. Also mention this in the cmake_policy() command documentation that explains how to set a policy to OLD. Suggested-by: Fraser Hutchison <fraser.hutchison@gmail.com>
22 lines
807 B
ReStructuredText
22 lines
807 B
ReStructuredText
CMP0001
|
|
-------
|
|
|
|
CMAKE_BACKWARDS_COMPATIBILITY should no longer be used.
|
|
|
|
The OLD behavior is to check CMAKE_BACKWARDS_COMPATIBILITY and present
|
|
it to the user. The NEW behavior is to ignore
|
|
CMAKE_BACKWARDS_COMPATIBILITY completely.
|
|
|
|
In CMake 2.4 and below the variable CMAKE_BACKWARDS_COMPATIBILITY was
|
|
used to request compatibility with earlier versions of CMake. In
|
|
CMake 2.6 and above all compatibility issues are handled by policies
|
|
and the cmake_policy command. However, CMake must still check
|
|
CMAKE_BACKWARDS_COMPATIBILITY for projects written for CMake 2.4 and
|
|
below.
|
|
|
|
This policy was introduced in CMake version 2.6.0. CMake version
|
|
|release| warns when the policy is not set and uses OLD behavior. Use
|
|
the cmake_policy command to set it to OLD or NEW explicitly.
|
|
|
|
.. include:: DEPRECATED.txt
|