blob: f9a2c53dcb37ac7183dccee43c9f0f8588ddfae3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
project(gammaray-plugin-examples)
cmake_minimum_required(VERSION 2.8.12)
set(CMAKE_AUTOMOC ON)
set(CMAKE_INCLUDE_CURRENT_DIR ON)
include(FeatureSummary)
find_package(GammaRay 2.6.50 REQUIRED NO_MODULE)
set_package_properties(GammaRay PROPERTIES
TYPE REQUIRED
URL "http://www.kdab.com/gammaray"
DESCRIPTION "Qt introspection tool"
PURPOSE "Needed to build custom GammaRay plug-ins."
)
# TODO: Work-around for CI where Qt5Ivi is installed into separate prefix
# Qt5IviCore pulls in Qt5Qml, but find_package inside there only checks $PWD/../; it does not honor CMAKE_PREFIX_PATH
# Pull in Qt5Qml manually, to honor CMAKE_PREFIX_PATH
# I consider this a bug in the generated CMake config files -- we should not set NO_DEFAULT_PATH there
find_package(Qt5Qml REQUIRED)
find_package(Qt5IviCore REQUIRED)
find_package(Qt5IviVehicleFunctions REQUIRED)
if(CMAKE_SYSTEM_NAME MATCHES Linux OR CMAKE_SYSTEM_NAME STREQUAL GNU)
if(CMAKE_COMPILER_IS_GNUCXX OR "${CMAKE_CXX_COMPILER_ID}" STREQUAL "Clang")
# more aggressive linker flags (for testing the GammaRay-provided development files for completeness)
set(CMAKE_SHARED_LINKER_FLAGS "-Wl,--fatal-warnings -Wl,--no-undefined -lc ${CMAKE_SHARED_LINKER_FLAGS}")
set(CMAKE_MODULE_LINKER_FLAGS "-Wl,--fatal-warnings -Wl,--no-undefined -lc ${CMAKE_MODULE_LINKER_FLAGS}")
# always a good idea
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall")
endif()
endif()
add_subdirectory(src)
feature_summary(WHAT ALL INCLUDE_QUIET_PACKAGES FATAL_ON_MISSING_REQUIRED_PACKAGES)
|
