aboutsummaryrefslogtreecommitdiff
path: root/tests/ECMSetupVersionTest
AgeCommit message (Collapse)Author
2021-08-06Add another test for ECMSetupVersionChristophe Giboudeaux
Amends: f0790f910 GIT_SILENT
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
2019-11-04Fix ECMSetupVersion tests for old policy with project() wo/ VERSIONFriedrich W. H. Kossebau
With min required cmake version now bumped to 3.5, the policy for CMP0048 needs to be set explicitly to old now to prepare what the tests check. Fixup for 5ca01895e3c50322f79feeef5054d7f28b164d68
2019-10-22Raise CMake requirements to 3.5Hannah von Reth
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-28Improve version file tests.Alex Merry
Mostly just refatoring to have less duplicated code.
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-12-07Fix ECMSetupVersionTest/new_explicit_header_abspathAlex Merry
The #include in the main.c file did not match the generated header file name, so it was actually incorrectly including the header from another test. BUG: 341576
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
generated by cgit v1.2.1 (git 2.18.0) at 2025-05-04 10:35:37 +0000