Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Help: Improve documentation links and formatting | Bartosz Kosiorek | 2019-03-27 | 1 | -7/+7 |
| | |||||
* | Help: Document explicitly that policy OLD behavior is deprecated | Brad King | 2015-06-09 | 1 | -0/+2 |
| | | | | | | | | | | | 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> | ||||
* | Help: Change version 3.0.0 -> 3.0 in policy docs | Brad King | 2014-02-10 | 1 | -2/+2 |
| | | | | | | Starting with 3.0 we will use only two components for the feature level, and policies are only ever introduced with a bump to the feature level version. | ||||
* | project: Manage VERSION variables | Brad King | 2014-01-29 | 1 | -0/+22 |
Teach the project() command to set variables {PROJECT,<PROJECT-NAME>}_VERSION{,_MAJOR,_MINOR,_PATCH,_TWEAK} holding the project version number and its components. Add project() command option "VERSION" to specify the version explicitly, and default to the empty string when it is not given. Since this clears variables when no VERSION is given, this may change behavior for existing projects that set the version variables themselves prior to calling project(). Add policy CMP0048 for compatibility. Suggested-by: Alex Neundorf <neundorf@kde.org> |