aboutsummaryrefslogtreecommitdiff
path: root/KF5ConfigConfig.cmake.in
diff options
context:
space:
mode:
authorAleix Pol <aleixpol@kde.org>2015-06-21 02:14:54 +0200
committerAleix Pol <aleixpol@kde.org>2015-06-21 02:14:54 +0200
commit173b33592739f9a671f34eb816499ef32fe65c06 (patch)
treed4dd33cee0d95dc5a3ef2b4ab023ba922af86e7e /KF5ConfigConfig.cmake.in
parenta5bb0860caf443cb89a7d4b67a040485e7509e74 (diff)
downloadkconfig-173b33592739f9a671f34eb816499ef32fe65c06.tar.gz
kconfig-173b33592739f9a671f34eb816499ef32fe65c06.tar.bz2
Make it possible to use kconfig_compiler from different sources
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
Diffstat (limited to 'KF5ConfigConfig.cmake.in')
-rw-r--r--KF5ConfigConfig.cmake.in7
1 files changed, 6 insertions, 1 deletions
diff --git a/KF5ConfigConfig.cmake.in b/KF5ConfigConfig.cmake.in
index b4e5f565..c1dd9af9 100644
--- a/KF5ConfigConfig.cmake.in
+++ b/KF5ConfigConfig.cmake.in
@@ -2,9 +2,14 @@
# Any changes in this ".cmake" file will be overwritten by CMake, the source is the ".cmake.in" file.
-
include("${CMAKE_CURRENT_LIST_DIR}/KF5ConfigTargets.cmake")
find_dependency(Qt5Xml "@REQUIRED_QT_VERSION@")
+if(CMAKE_CROSSCOMPILING AND KF5_HOST_TOOLING)
+ find_file(KCONFIGCOMPILER_PATH KF5Config/KF5ConfigCompilerTargets.cmake PATHS ${KF5_HOST_TOOLING} ${CMAKE_CURRENT_LIST_DIR} NO_DEFAULT_PATH)
+ include("${TARGETSFILE}")
+else()
+ include("${CMAKE_CURRENT_LIST_DIR}/KF5ConfigCompilerTargets.cmake")
+endif()
include("${CMAKE_CURRENT_LIST_DIR}/KF5ConfigMacros.cmake")