mirror of
https://github.com/reactos/CMake.git
synced 2024-12-14 15:19:39 +00:00
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>
25 lines
1.0 KiB
ReStructuredText
25 lines
1.0 KiB
ReStructuredText
CMP0048
|
|
-------
|
|
|
|
The :command:`project` command manages VERSION variables.
|
|
|
|
CMake version 3.0 introduced the ``VERSION`` option of the :command:`project`
|
|
command to specify a project version as well as the name. In order to keep
|
|
:variable:`PROJECT_VERSION` and related variables consistent with variable
|
|
:variable:`PROJECT_NAME` it is necessary to set the VERSION variables
|
|
to the empty string when no ``VERSION`` is given to :command:`project`.
|
|
However, this can change behavior for existing projects that set VERSION
|
|
variables themselves since :command:`project` may now clear them.
|
|
This policy controls the behavior for compatibility with such projects.
|
|
|
|
The OLD behavior for this policy is to leave VERSION variables untouched.
|
|
The NEW behavior for this policy is to set VERSION as documented by the
|
|
:command:`project` command.
|
|
|
|
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 cmake_policy command to set it to OLD or
|
|
NEW explicitly.
|
|
|
|
.. include:: DEPRECATED.txt
|