2019-06-05 08:08:44 +00:00
|
|
|
cmake_minimum_required(VERSION 3.15.0)
|
2019-01-30 10:12:21 +00:00
|
|
|
|
2019-06-20 12:15:59 +00:00
|
|
|
if(DEFINED ENV{VCPKG_ROOT})
|
|
|
|
|
set(vcpkg_toolchain_file "$ENV{VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake")
|
|
|
|
|
get_filename_component(vcpkg_toolchain_file "${vcpkg_toolchain_file}" ABSOLUTE)
|
|
|
|
|
|
|
|
|
|
if(DEFINED CMAKE_TOOLCHAIN_FILE)
|
|
|
|
|
get_filename_component(supplied_toolchain_file "${CMAKE_TOOLCHAIN_FILE}" ABSOLUTE)
|
|
|
|
|
if(NOT supplied_toolchain_file STREQUAL vcpkg_toolchain_file)
|
|
|
|
|
set(VCPKG_CHAINLOAD_TOOLCHAIN_FILE "${CMAKE_TOOLCHAIN_FILE}" CACHE STRING "")
|
|
|
|
|
endif()
|
|
|
|
|
unset(supplied_toolchain_file)
|
|
|
|
|
endif()
|
|
|
|
|
set(CMAKE_TOOLCHAIN_FILE "${vcpkg_toolchain_file}" CACHE STRING "" FORCE)
|
|
|
|
|
message(STATUS "Using vcpkg from $ENV{VCPKG_ROOT}")
|
|
|
|
|
if(DEFINED ENV{VCPKG_DEFAULT_TRIPLET} AND NOT DEFINED VCPKG_TARGET_TRIPLET)
|
|
|
|
|
set(VCPKG_TARGET_TRIPLET "$ENV{VCPKG_DEFAULT_TRIPLET}" CACHE STRING "")
|
|
|
|
|
message(STATUS "Using vcpkg triplet ${VCPKG_TARGET_TRIPLET}")
|
|
|
|
|
endif()
|
|
|
|
|
unset(vcpkg_toolchain_file)
|
2019-06-20 11:23:19 +00:00
|
|
|
endif()
|
|
|
|
|
|
2018-10-24 13:20:27 +00:00
|
|
|
project(QtBase
|
2019-06-14 10:59:07 +00:00
|
|
|
VERSION 6.0.0
|
2018-10-24 13:20:27 +00:00
|
|
|
DESCRIPTION "Qt Base Libraries"
|
|
|
|
|
HOMEPAGE_URL "https://qt.io/"
|
2019-02-11 14:02:05 +00:00
|
|
|
LANGUAGES CXX C ASM
|
2018-10-24 13:20:27 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
## Add some paths to check for cmake modules:
|
2019-06-06 07:03:48 +00:00
|
|
|
list(PREPEND CMAKE_MODULE_PATH
|
2018-11-01 09:43:05 +00:00
|
|
|
"${CMAKE_CURRENT_SOURCE_DIR}/cmake"
|
|
|
|
|
"${CMAKE_CURRENT_SOURCE_DIR}/cmake/3rdparty/extra-cmake-modules/find-modules"
|
|
|
|
|
"${CMAKE_CURRENT_SOURCE_DIR}/cmake/3rdparty/kwin"
|
|
|
|
|
)
|
2018-10-24 13:20:27 +00:00
|
|
|
|
2019-05-15 11:57:15 +00:00
|
|
|
## Find the build internals package.
|
2019-06-06 07:03:48 +00:00
|
|
|
list(PREPEND CMAKE_PREFIX_PATH
|
2019-05-15 11:57:15 +00:00
|
|
|
"${CMAKE_CURRENT_SOURCE_DIR}/cmake"
|
|
|
|
|
)
|
2019-05-29 14:05:52 +00:00
|
|
|
find_package(QtBuildInternals CMAKE_FIND_ROOT_PATH_BOTH)
|
2018-10-24 13:20:27 +00:00
|
|
|
|
2019-05-15 11:57:15 +00:00
|
|
|
qt_build_repo_begin(SKIP_CMAKE_MODULE_PATH_ADDITION)
|
2018-10-24 13:20:27 +00:00
|
|
|
|
|
|
|
|
## QtBase specific configure tests:
|
|
|
|
|
include(QtBaseConfigureTests)
|
|
|
|
|
|
2018-11-14 12:37:52 +00:00
|
|
|
## Build System tests:
|
|
|
|
|
include(QtBaseCMakeTesting)
|
|
|
|
|
|
2018-10-24 13:20:27 +00:00
|
|
|
## Targets for global features, etc.:
|
|
|
|
|
include(QtBaseGlobalTargets)
|
|
|
|
|
|
|
|
|
|
## Should this Qt be static or dynamically linked?
|
|
|
|
|
option(BUILD_SHARED_LIBS "Build Qt statically or dynamically" ON)
|
|
|
|
|
set(QT_BUILD_SHARED_LIBS ${BUILD_SHARED_LIBS})
|
|
|
|
|
|
2019-06-04 13:14:42 +00:00
|
|
|
## Should this Qt be built with Werror?
|
|
|
|
|
option(WARNINGS_ARE_ERRORS "Build Qt with warnings as errors" ${FEATURE_developer_build})
|
|
|
|
|
|
Export tool config and target files for each relevant module
CMake will now generate config and target files for each module that
provides tools. As a result, namespaced global targets such as
Qt5::moc or Qt5::rcc can be made available.
Third party projects that require just these tools, and not the Qt
modules themselves, should specify CMAKE_PREFIX_PATH pointing to the
installed Qt location, and call find_package(Qt5CoreTools),
find_package(Qt5GuiTools), etc.
It is also possible to call
find_package(Qt5Tools REQUIRED Core Widgets) where the last option
is a list of modules whose tools should be imported.
Note that all the tools are in the Qt5::
namespace and not in the Qt5CoreTools:: or Qt5WidgetsTools::
namespace.
This commit also changes the behavior regarding when to build tools
while building Qt itself.
When cross compiling Qt (checked via CMAKE_CROSSCOMPILING) or when
-DQT_FORCE_FIND_TOOLS=TRUE is passed, tools added by add_qt_tool will
always be searched for and not built.
In this case the user has to specify the CMake variable QT_HOST_PATH
pointing to an installed host Qt location.
When not cross compiling, tools added by add_qt_tool are built from
source.
When building leaf modules (like qtsvg) that require some tool that was
built in qtbase (like moc), the module project should contain a
find_package(Qt5ToolsCore) call and specify an appropriate
CMAKE_PREFIX_PATH so that the tool package is found.
Note that because HOST_QT_TOOLS_DIRECTORY was replaced by QT_HOST_PATH,
the ensure syncqt code was changed to make it work properly with
both qtbase and qtsvg.
Here's a list of tools and their module associations:
qmake, moc, rcc, tracegen, qfloat16-tables, qlalr -> CoreTools
qvkgen -> GuiTools
uic -> WidgetTools
dbus related tools -> DBusTools
Task-number: QTBUG-74134
Change-Id: Ie67d1e2f8de46102b48eca008f0b50caf4fbe3ed
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
2019-04-10 17:21:22 +00:00
|
|
|
## Decide whether tools will be built.
|
|
|
|
|
qt_check_if_tools_will_be_built()
|
|
|
|
|
|
2018-10-24 13:20:27 +00:00
|
|
|
## Visit all the directories:
|
|
|
|
|
add_subdirectory(src)
|
|
|
|
|
|
|
|
|
|
if (BUILD_TESTING)
|
|
|
|
|
add_subdirectory(tests)
|
|
|
|
|
endif()
|
|
|
|
|
|
Export tool config and target files for each relevant module
CMake will now generate config and target files for each module that
provides tools. As a result, namespaced global targets such as
Qt5::moc or Qt5::rcc can be made available.
Third party projects that require just these tools, and not the Qt
modules themselves, should specify CMAKE_PREFIX_PATH pointing to the
installed Qt location, and call find_package(Qt5CoreTools),
find_package(Qt5GuiTools), etc.
It is also possible to call
find_package(Qt5Tools REQUIRED Core Widgets) where the last option
is a list of modules whose tools should be imported.
Note that all the tools are in the Qt5::
namespace and not in the Qt5CoreTools:: or Qt5WidgetsTools::
namespace.
This commit also changes the behavior regarding when to build tools
while building Qt itself.
When cross compiling Qt (checked via CMAKE_CROSSCOMPILING) or when
-DQT_FORCE_FIND_TOOLS=TRUE is passed, tools added by add_qt_tool will
always be searched for and not built.
In this case the user has to specify the CMake variable QT_HOST_PATH
pointing to an installed host Qt location.
When not cross compiling, tools added by add_qt_tool are built from
source.
When building leaf modules (like qtsvg) that require some tool that was
built in qtbase (like moc), the module project should contain a
find_package(Qt5ToolsCore) call and specify an appropriate
CMAKE_PREFIX_PATH so that the tool package is found.
Note that because HOST_QT_TOOLS_DIRECTORY was replaced by QT_HOST_PATH,
the ensure syncqt code was changed to make it work properly with
both qtbase and qtsvg.
Here's a list of tools and their module associations:
qmake, moc, rcc, tracegen, qfloat16-tables, qlalr -> CoreTools
qvkgen -> GuiTools
uic -> WidgetTools
dbus related tools -> DBusTools
Task-number: QTBUG-74134
Change-Id: Ie67d1e2f8de46102b48eca008f0b50caf4fbe3ed
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
2019-04-10 17:21:22 +00:00
|
|
|
if (QT_WILL_BUILD_TOOLS)
|
2019-02-15 12:16:35 +00:00
|
|
|
add_subdirectory(qmake)
|
|
|
|
|
endif()
|
2019-01-17 09:22:59 +00:00
|
|
|
|
2019-06-21 14:45:37 +00:00
|
|
|
# As long as we use the mkspecs (for qplatformdefs.h), we need to always
|
|
|
|
|
# install it, especially when cross-compiling.
|
|
|
|
|
set(mkspecs_install_dir "${INSTALL_DATADIR}")
|
|
|
|
|
qt_path_join(mkspecs_install_dir ${QT_INSTALL_DIR} ${mkspecs_install_dir})
|
|
|
|
|
|
|
|
|
|
qt_copy_or_install(DIRECTORY "${PROJECT_SOURCE_DIR}/mkspecs"
|
|
|
|
|
DESTINATION ${mkspecs_install_dir})
|
|
|
|
|
|
|
|
|
|
|
2019-06-11 13:46:31 +00:00
|
|
|
qt_build_repo_end()
|
|
|
|
|
|
2019-01-17 09:22:59 +00:00
|
|
|
option(BUILD_EXAMPLES "Build Qt examples" ON)
|
|
|
|
|
if (BUILD_EXAMPLES)
|
|
|
|
|
add_subdirectory(examples)
|
|
|
|
|
endif()
|
