| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
This way we can specify the used tooling targets to be used, useful if we're
cross-compiling, since we get to use the tooling that runs in the local
platform.
REVIEW: 124104
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
like all the other Qt-based modules do
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Drop KCoreAddons and KI18n dependency.
Add a bunch of QStringLiteral()
|
|
|
|
the version in two steps at release time, so CI doesn't break
|
|
This is instead of INCLUDE_INSTALL_DIR and INSTALL_TARGETS_DEFAULT_ARGS,
which will lose the "KF5" suffix from the include path.
|
|
|
|
|
|
Just because the executable has the "_kf5" suffix, that does not mean
the target should have it. This is ugly API, and will be unnecessary
porting effort for KF6.
REVIEW: 116995
|
|
|
|
|
|
|
|
Ported with:
sed -i -e 's/\(include(\)CMake\(PackageConfigHelpers)\)/\1ECM\2/' \
-e 's/\<\(configure_package_config_file\)/ecm_\1/' \
CMakeLists.txt
See http://commits.kde.org/extra-cmake-modules/139f60d81653888f696ef433
|
