extra-cmake-modules.git, branch v1.6.0-rc1 hurd extra-cmake-modules.git Fix include directory change spotted by Hrvoje Senjan. 2014-12-28T17:34:30+00:00 Alex Merry alex.merry@kde.org 2014-12-28T17:34:30+00:00 8dc36cfa882f07a60b3ebdf16d9aac57871bd382 A previous commit inadvertantly changed the KF5 include prefix to kf5 (uppercase to lowercase). 
A previous commit inadvertantly changed the KF5 include prefix to kf5
(uppercase to lowercase).
Improve version file tests. 2014-12-28T17:30:11+00:00 Alex Merry alex.merry@kde.org 2014-12-28T16:32:13+00:00 f8af407eba5c5ea45be2c6351cf41a7cb44fed21 Mostly just refatoring to have less duplicated code. 
Mostly just refatoring to have less duplicated code.
Add deprecation warnings for old-style variables. 2014-12-28T15:44:35+00:00 Alex Merry alex.merry@kde.org 2014-12-24T18:31:05+00:00 351fe45dba7ac04ec2779b7d761ac55a58f89945 REVIEW: 121646 
REVIEW: 121646
Refactor KDEInstallDirs tests. 2014-12-28T15:44:32+00:00 Alex Merry alex.merry@kde.org 2014-12-23T16:07:41+00:00 25d2b72789090e99b0059784827e43a1a82aeafb REVIEW: 121646 
REVIEW: 121646
Make KDEInstallDirs provide KDE_INSTALL_* variables. 2014-12-28T15:43:52+00:00 Alex Merry alex.merry@kde.org 2014-12-17T20:33:32+00:00 107f255620b6284de118aa1f358ab6cf99862ae9 Creating variables whose names start with CMAKE_ is a bad idea for modules distributed outside CMake itself. Since the module is called KDEInstallDirs, having a KDE_INSTALL_ prefix for the variables is clear and intuitive. Both CMAKE_INSTALL_* variables and the older KDELibs4-compatible variables are provided, unless KDE_INSTALL_DIRS_NO_DEPRECATED is set to TRUE before the module is included. Even then, the CMAKE_INSTALL_* variables provided by the GNUInstallDirs module will still be set and understood (for compatibility with that module), unless KDE_INSTALL_DIRS_NO_CMAKE_VARIABLES is set to TRUE. REVIEW: 121646 
Creating variables whose names start with CMAKE_ is a bad idea for
modules distributed outside CMake itself. Since the module is called
KDEInstallDirs, having a KDE_INSTALL_ prefix for the variables is clear
and intuitive.

Both CMAKE_INSTALL_* variables and the older KDELibs4-compatible
variables are provided, unless KDE_INSTALL_DIRS_NO_DEPRECATED is set to
TRUE before the module is included. Even then, the CMAKE_INSTALL_*
variables provided by the GNUInstallDirs module will still be set and
understood (for compatibility with that module), unless
KDE_INSTALL_DIRS_NO_CMAKE_VARIABLES is set to TRUE.

REVIEW: 121646
Fix formatting in ECMSetupVersion.cmake. 2014-12-28T15:04:15+00:00 Alex Merry alex.merry@kde.org 2014-12-27T15:41:49+00:00 69939eef4f828e881edd387b129128cb252f7ab3 






Add COMPATIBILITY argument to ecm_setup_version().
2014-12-28T15:03:31+00:00

Alex Merry
alex.merry@kde.org

2014-12-27T15:28:39+00:00

bd69cdeea9aef1f254b7d83dd137a4de955151b7

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





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







Upgrade ECM version to 1.6.0.
2014-12-17T16:23:12+00:00

l10n daemon script
scripty@kde.org

2014-12-17T16:23:10+00:00

fe771709d774402e4cdeb883c2783f64b6e62d65












Fix ECMQueryQmake when Qt5Core is found.
2014-12-07T19:17:34+00:00

Alex Merry
alex.merry@kde.org

2014-12-07T19:17:34+00:00

fd7aa7e8eab35c81faaeb8346a57b73dd63f4efb

81627ad86d3d7d5e5a7d130dfc746d5b1b58cbe7 broke the case where Qt5 qmake
is not in the path or not called qmake-qt5, because it stopped using the
location of qmake as provided by the Qt5Core CMake module when found.





81627ad86d3d7d5e5a7d130dfc746d5b1b58cbe7 broke the case where Qt5 qmake
is not in the path or not called qmake-qt5, because it stopped using the
location of qmake as provided by the Qt5Core CMake module when found.







Fix ECMSetupVersionTest/new_explicit_header_abspath
2014-12-07T18:44:54+00:00

Alex Merry
alex.merry@kde.org

2014-12-07T18:44:54+00:00

b5f3c66c8182e2ca2d0670d3e0962bc215fea220

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





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