extra-cmake-modules.git/modules, branch v5.29.0 hurd extra-cmake-modules.git Fix typo 2016-12-01T10:14:22+00:00 Elvis Angelaccio elvis.angelaccio@kde.org 2016-12-01T10:14:22+00:00 78fc8f7a22cf1f6a091ccc3b94c6e2dff038f8bd GIT_SILENT 
GIT_SILENT
Minor: Remove extra new line 2016-11-18T17:33:21+00:00 Kevin Funk kfunk@kde.org 2016-11-18T17:33:21+00:00 751b6abcc5a750c0fd75d393f8d13c6167c89728 Triggered my OCD 
Triggered my OCD
Add ecm_win_resolve_symlinks module. 2016-11-05T14:38:05+00:00 Gleb Popov 6yearold@gmail.com 2016-06-06T17:54:50+00:00 632b8868de38e2f85fb4969bcae3dd89a2a0695c REVIEW: 128112 
REVIEW: 128112
ecm_process_po_files_as_qm: Skip fuzzy translations 2016-09-05T12:02:11+00:00 Alexander Potashev aspotashev@gmail.com 2016-09-05T12:02:11+00:00 ee35b6c12a8f05136ea7d69961e34a9d531d97b6 REVIEW: 128823 
REVIEW: 128823
The default level for logging categories should be Info rather than Warning. 2016-09-02T14:36:00+00:00 David Faure faure@kde.org 2016-06-17T22:23:40+00:00 413eb26f5d9e7a7f174509f8a16d057d5c0e6578 The whole point of Info is to be used by apps who want to print out some info for the user, not disabled by default. Example use case: ksmserver could output the name of the autostart files it's starting, so user can check their own scripts are started, and associate any errors with the corresponding script. In other words: Debug = debugging for the developer Info = debugging for the user :-) This commit shows the benefit of having a central place for changing this (many category definitions do not use this macro though) REVIEW: 128232 
The whole point of Info is to be used by apps who want to print out some
info for the user, not disabled by default.

Example use case: ksmserver could output the name of the autostart
files it's starting, so user can check their own scripts are started,
and associate any errors with the corresponding script.

In other words:
Debug = debugging for the developer
Info = debugging for the user :-)

This commit shows the benefit of having a central place for changing this
(many category definitions do not use this macro though)

REVIEW: 128232
add full license text 2016-08-31T21:00:09+00:00 Allen Winter winter@kde.org 2016-08-31T21:00:09+00:00 040440eb9ebfa756adc6b31f53d8e733fd0da3c9 REVIEW: 128780 
REVIEW: 128780
Fix inclusion when there's no Qt5 2016-07-26T23:44:31+00:00 Aleix Pol aleixpol@kde.org 2016-07-26T23:44:31+00:00 c07196c98c6998813fee3ab2889bba5d36447f58 ECMQueryQmake will fail as it's designed to only work with Qt5. We don't want to terminate the execution there, just to spit a warning and leave. If we suggest qmake-qt5 as a command, we'll end up performing the call anyway. This will fix the ExecuteCoreModules test under latest-qt4 build. 
ECMQueryQmake will fail as it's designed to only work with Qt5. We
don't want to terminate the execution there, just to spit a warning
and leave. If we suggest qmake-qt5 as a command, we'll end up performing
the call anyway.

This will fix the ExecuteCoreModules test under latest-qt4 build.
Add a fallback method for query_qmake() when there's no Qt5 installation 2016-07-26T12:06:56+00:00 Aleix Pol aleixpol@kde.org 2016-07-26T12:06:56+00:00 8ac7abb78d97210c5cbbc87fba83d58d7b843a8d Addresses its usage on systems where Qt5 isn't installed, it allows for modules using it to decide what they should do. REVIEW: 128488 
Addresses its usage on systems where Qt5 isn't installed, it allows for
modules using it to decide what they should do.

REVIEW: 128488
Make sure ECMGeneratePriFile.cmake behaves like the rest of ECM 2016-07-18T12:45:20+00:00 Aleix Pol aleixpol@kde.org 2016-07-18T12:45:02+00:00 5bb92992317a6cf878c823cadac6dd0ccff969d6 In KDEInstallDirs we have some code to make sure that qmake is asked when the project shares the prefix with the installed Qt, to make sure that if something was changed in the distribution it would reflect on the projects. Make sure PRI files are installed using the same reasoning. REVIEW: 128427 
In KDEInstallDirs we have some code to make sure that qmake is asked when
the project shares the prefix with the installed Qt, to make sure that if
something was changed in the distribution it would reflect on the projects.

Make sure PRI files are installed using the same reasoning.

REVIEW: 128427
ecm_qt_declare_logging_category: improve error message when using without including 2016-04-03T20:41:42+00:00 David Faure faure@kde.org 2016-03-20T10:52:27+00:00 f7c1e8d57f84d0883a2a7683fd59ecc990a03de1 If one subdir in the project includes this file, all others can use the function but they don't see the value of the variable, which leads to a strange error CMake Error at ECM/modules/ECMQtDeclareLoggingCategory.cmake:114 (configure_file): configure_file input location <srcdir> is a directory but a file was expected. Happened in KIO, with kio/gui doing include+function call, and then adding function call in kio/widgets. REVIEW: 127432 
If one subdir in the project includes this file, all others can use the function
but they don't see the value of the variable, which leads to a strange error

CMake Error at ECM/modules/ECMQtDeclareLoggingCategory.cmake:114 (configure_file):
  configure_file input location <srcdir> is a directory but a file was expected.

Happened in KIO, with kio/gui doing include+function call, and then adding
function call in kio/widgets.

REVIEW: 127432