extra-cmake-modules.git/modules, branch v1.8.0-rc1

Use lconvert path from Qt cmake config when on Qt >= 5.3.1

2015-03-06T11:14:56+00:00

Qt5LinguistToolsConfig.cmake defines CMake target for lconvert since Qt 5.3.1,
so we should use that if it is available.

Our own hacks were not working in some configurations (i.e. when there is
/usr/bin/lconvert managed by qtchooser, but no qtchooser configuration file).

REVIEW: 122626

Improve ECMPackageConfigHelpers documentation.

2015-02-28T10:37:45+00:00

In particular, strongly recommend looking at the equivalent CMake
documentation with regard to PATH_VARS, as a lot of projects that should
be making use of it are not.

Extend ecm_generate_headers macro to also support CamelCase.h headers

2015-02-15T20:45:34+00:00

REVIEW: 122317

Thanks alexmerry and dvratil for review

Minor: Cleanup

2015-02-06T14:00:52+00:00

Add missing documentation.

2015-02-06T11:51:57+00:00

Three modules (ECMCoverageOption, ECMEnableSanitizers and
ECMGeneratePkgConfigFile) were not being documented. This commit fixes
that situation.

Document when modules were added to ECM.

2015-02-06T11:51:56+00:00

Add a module to provide an uninstall target.

2015-02-04T18:29:47+00:00

This is basically just the code available on the CMake FAQ item about
`make uninstall`, but packaged up in a convenient module.

REVIEW: 122359

Minor documentation syntax fixes.

2015-02-01T12:04:08+00:00

Revert "Add SameMajorVersionWithPreleases compat option to ecm_setup_version."

2015-01-24T14:47:59+00:00

This reverts commit 959c374c022394a116e8ceb2b1fce2df11752068.

I merged and pushed the wrong branch.

Add SameMajorVersionWithPreleases compat option to ecm_setup_version.

2015-01-24T14:45:33+00:00

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.