aboutsummaryrefslogtreecommitdiff
path: root/modules/ECMSetupVersion.cmake
AgeCommit message (Collapse)Author
2021-08-05Simplify the PROJECT_VERSION regexChristophe Giboudeaux
CMake rejects the project version if it contains anything but dots and numbers, there's no need to try to catch anything else.
2021-08-05Handle case where zero must be keptChristophe Giboudeaux
This is required for the frameworks versions Amends: a0f8e54
2021-08-05ecm_setup_version: deal with 0-prefixed version values in PROJECT modeFriedrich W. H. Kossebau
5c191fa1d2383c69ddc075395e04f84b7679613a already added the same sanity check for the non-PROJECT mode
2021-05-25Clean ECM files after the minimum version changeChristophe Giboudeaux
- Remove deprecated version checks - Use VERSION_GREATER_EQUAL
2021-05-10ECMSetupVersion: phase out deprecated *_VERSION_STRING CMake variablesFriedrich W. H. Kossebau
2021-04-23Modules docs: move rst docs into bracket commentsFriedrich W. H. Kossebau
CMake >= 3.0 supports bracket comments, and the reStructuredText integration code in sphinx/ext/ecm.py already supports extracting the docs from a bracket comment instead. Editing documentation without leading line comment markers is more simple, e,g. when reflowing text over lines. With ECM meanwhile requiring CMake 3.5 now it is possible to switch (and thus follow also the approach used by cmake itself). NO_CHANGELOG
2020-08-30Strip leading zeros from numerical version numbers in C++ codev5.74.0-rc1v5.74.0Volker Krause
Our August releases produce invalid octal numbers ("08") otherwise.
2020-06-14extra-cmake-modules: Convert to SPDX license statementsAndreas Cord-Landwehr
2019-09-18API dox: fix ":" to "::"Friedrich W. H. Kossebau
As intended by original code, to generate consistent output per this document for the given lists of variables GIT_SILENT
2018-05-14Fix minor documentation typosMaximiliano Curia
Summary: These typos show up in the generated manpages. Reviewers: #frameworks, alexmerry, kossebau, cgiboudeaux Reviewed By: cgiboudeaux Subscribers: cgiboudeaux, kde-frameworks-devel, kde-buildsystem Tags: #frameworks, #build_system Differential Revision: https://phabricator.kde.org/D12867
2016-08-31add full license textAllen Winter
REVIEW: 128780
2015-02-06Document when modules were added to ECM.Alex Merry
2015-01-24Revert "Add SameMajorVersionWithPreleases compat option to ecm_setup_version."Alex Merry
This reverts commit 959c374c022394a116e8ceb2b1fce2df11752068. I merged and pushed the wrong branch.
2015-01-24Add SameMajorVersionWithPreleases compat option to ecm_setup_version.Alex Merry
SameMajorVersionWithPreleases is intended implement the versioning scheme followed by many KDE projects: minor releases after some high number (eg: 90) are considered to be pre-releases of the next major version, and are not compatible with the current major version. This allows alpha and beta releases to be ordered correctly by version-number-aware software like package managers (an alpha of version 2 should have a higher number than any release of version 1, but less than version 2.0). So a request for version 2.1.0 of a piece of software should not be satisfied by 2.93.4, because that is actually a pre-release of version 3. On the other hand, a request for version 2.91.0 should be satisfied by version 3.1.0. Note that prereleases are not considered unless explicitly requested, so 2.93.4 will not satisfy requests for version 3 (or version 2) of a piece of software.
2014-12-28Fix formatting in ECMSetupVersion.cmake.Alex Merry
2014-12-28Add COMPATIBILITY argument to ecm_setup_version().Alex Merry
Lots of libraries will want to use SameMajorVersion to make sure searching for version 1 of a library doesn't give you version 2, for example. We may want to add another, custom compatibility mode for KDE Frameworks-style versioning, where version x.90.z to x.99.z are alpha/beta releases for version (x+1). REVIEW: 121696
2014-04-25Fix ecm_setup_version() with CMake 2.8.12.xAlex Merry
cmake_policy() does not allow you to reference policies that do not yet exist, so include a version check.
2014-04-25Make ecm_setup_version interact well with CMP0048Alex Merry
When CMake policy CMP0048 (CMake 3.0) is set to NEW, the project() command is meant to manage the project's version variables. We therefore do not set the PROJECT_VERSION variables in this case. To make sure projects do not have to specify their version in multiple places, this also allows the keyword "PROJECT" to be passed to ecm_setup_version instead of an actual version number. In this case, the version passed to project() will be used. REVIEW: 117619
2014-04-11Add documentation generation using SphinxAlex Merry
This is deliberately modelled very closely on CMake's documentation system. It's a hefty patch, because it involved changing all the documentation to be in reStructuredText format. I also cleaned up the copyright/license statements at the same time. Note that the find modules contain the full license, due to the fact that ecm_use_find_module() copies them out of the ECM distribution.
2014-01-25Make ECMSetupVersion set PROJECT_VERSION_*David Faure
This makes it easier for other functions to access the project version, for instance my upcoming ECM_GENERATE_PRI_FILE()
2014-01-10Rename ECM_VERSION_* to PROJECT_VERSION_* to avoid confusion with ECM's own ↵David Faure
version This is all internal, doesn't change the API or effects of ecm_setup_version.
2013-10-01Remove compatibility signature from ECMSetupVersion.Stephen Kelly
2013-09-26Change the signature of the ecm_setup_version macro.Stephen Kelly
Accept a single version argument instead of three. The old signature will be an error in a few days.
2012-11-25-fix: ecm_setup_version() has no multi-value argumentsAlex Neundorf
Alex
2012-11-23increase version to 0.0.6Alex Neundorf
This commit -adds the macro ecm_setup_version(), as proposed on the kde-frameworks list -sets CMAKE_INSTALL_DEFAULT_COMPONENT_NAME to ${PROJECT_NAME} if a project has been set -makes e-c-m require cmake 2.8.10.1 Alex
generated by cgit v1.2.1 (git 2.18.0) at 2025-05-04 09:47:54 +0000