2020-02-04 15:19:18 +00:00
|
|
|
# special case skip regeneration
|
2019-06-05 08:08:44 +00:00
|
|
|
cmake_minimum_required(VERSION 3.15.0)
|
2019-01-30 10:12:21 +00:00
|
|
|
|
2020-10-09 09:48:23 +00:00
|
|
|
# Run auto detection routines, but not when doing standalone tests. In that case, the detection
|
|
|
|
# results are taken from either QtBuildInternals or the qt.toolchain.cmake file. Also, inhibit
|
|
|
|
# auto-detection in a top-level build, because the top-level project file already includes it.
|
|
|
|
if(NOT QT_BUILD_STANDALONE_TESTS AND NOT QT_SUPER_BUILD)
|
2020-06-02 16:06:37 +00:00
|
|
|
include(${CMAKE_CURRENT_SOURCE_DIR}/cmake/QtAutoDetect.cmake)
|
|
|
|
endif()
|
2019-06-20 11:23:19 +00:00
|
|
|
|
2020-08-13 10:05:13 +00:00
|
|
|
include(".cmake.conf")
|
|
|
|
project(QtBase
|
|
|
|
VERSION "${QT_REPO_MODULE_VERSION}"
|
|
|
|
DESCRIPTION "Qt Base Libraries"
|
|
|
|
HOMEPAGE_URL "https://qt.io/"
|
|
|
|
LANGUAGES CXX C ASM
|
|
|
|
)
|
|
|
|
|
2020-09-22 10:11:13 +00:00
|
|
|
# Make sure we only use latest private CMake API, aka no compatibility wrappers.
|
|
|
|
set(QT_NO_INTERNAL_COMPATIBILITY_FUNCTIONS TRUE)
|
|
|
|
|
2020-03-25 12:43:33 +00:00
|
|
|
if (CMAKE_CROSSCOMPILING AND CMAKE_SYSROOT)
|
|
|
|
# When cross compiling with CMake any calls to pkg_check_modules() will
|
|
|
|
# search into the host system instead of the target sysroot.
|
|
|
|
# The current work around is based on the discussion found at
|
|
|
|
# https://gitlab.kitware.com/cmake/cmake/-/merge_requests/4478
|
|
|
|
set(ENV{PKG_CONFIG_DIR} "")
|
|
|
|
set(ENV{PKG_CONFIG_LIBDIR} "${CMAKE_SYSROOT}/usr/lib/${CMAKE_LIBRARY_ARCHITECTURE}/pkgconfig")
|
|
|
|
set(ENV{PKG_CONFIG_SYSROOT_DIR} ${CMAKE_SYSROOT})
|
|
|
|
endif()
|
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
if(NOT QT_BUILD_STANDALONE_TESTS)
|
|
|
|
## Add some paths to check for cmake modules:
|
|
|
|
list(PREPEND CMAKE_MODULE_PATH
|
|
|
|
"${CMAKE_CURRENT_SOURCE_DIR}/cmake"
|
|
|
|
"${CMAKE_CURRENT_SOURCE_DIR}/cmake/3rdparty/extra-cmake-modules/find-modules"
|
|
|
|
"${CMAKE_CURRENT_SOURCE_DIR}/cmake/3rdparty/kwin"
|
|
|
|
)
|
|
|
|
|
2020-03-16 12:36:47 +00:00
|
|
|
if(MACOS)
|
cmake: Add default Info.plist for macOS with some important keys
The default Info.plist shipped with CMake lacks an NSPrincipalClass
entry, which is crucial for making macOS apps run in full resolution
on retina screens.
We make sure the file is only picked up on macOS, not iOS and friends,
since those platforms require another principal class. If needed we can
extract the value out as a CMake variable and use the same file for all
Apple platforms. Doing so would assume all keys are single-platform
only, so if that's not the case we need platform-specific files.
We should probably extract the package type out as a variable too,
so that the file can be used for both apps, plugins, and frameworks,
but doing so requires setting up that variable somewhere based on
the target type, which CMake doesn't allow in an easy way.
The file itself is based on the file CMake ships, combined with
keys inherited from Qt's existing plist templates for qmake, and
adjusted to match what Xcode generates by default these days.
Change-Id: I3f5109e5fff63cdbd109a99d4008948d4bd2102b
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2020-03-11 20:45:50 +00:00
|
|
|
# Add module directory to pick up custom Info.plist template
|
|
|
|
list(APPEND CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/cmake/macos")
|
|
|
|
endif()
|
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
## Find the build internals package.
|
|
|
|
set(QT_BUILD_INTERNALS_SKIP_CMAKE_MODULE_PATH_ADDITION TRUE)
|
|
|
|
list(PREPEND CMAKE_PREFIX_PATH
|
|
|
|
"${CMAKE_CURRENT_SOURCE_DIR}/cmake"
|
|
|
|
)
|
|
|
|
find_package(QtBuildInternals CMAKE_FIND_ROOT_PATH_BOTH)
|
|
|
|
unset(QT_BUILD_INTERNALS_SKIP_CMAKE_MODULE_PATH_ADDITION)
|
|
|
|
else()
|
|
|
|
# When building standalone tests, an istalled BuildInternals package already exists.
|
|
|
|
find_package(Qt6 REQUIRED COMPONENTS BuildInternals CMAKE_FIND_ROOT_PATH_BOTH)
|
|
|
|
endif()
|
2018-10-24 13:20:27 +00:00
|
|
|
|
2019-09-26 15:58:53 +00:00
|
|
|
qt_build_repo_begin()
|
2018-10-24 13:20:27 +00:00
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
if(NOT QT_BUILD_STANDALONE_TESTS)
|
|
|
|
## 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-11-07 07:51:03 +00:00
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
## Should this Qt be built with Werror?
|
|
|
|
option(WARNINGS_ARE_ERRORS "Build Qt with warnings as errors" ${FEATURE_developer_build})
|
2019-11-07 07:51:03 +00:00
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
## QtBase specific configure tests:
|
|
|
|
include(QtBaseConfigureTests)
|
2018-11-14 12:37:52 +00:00
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
## Build System tests:
|
|
|
|
include(QtBaseCMakeTesting)
|
2018-10-24 13:20:27 +00:00
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
## Targets for global features, etc.:
|
|
|
|
include(QtBaseGlobalTargets)
|
2019-10-17 08:14:09 +00:00
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
## Set language standards after QtBaseGlobalTargets, because that's when the relevant
|
|
|
|
## feature variables are available.
|
|
|
|
qt_set_language_standards()
|
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
|
|
|
|
2019-11-26 09:10:55 +00:00
|
|
|
#include CoreMacros() for qt6_generate_meta_types()
|
2020-08-21 14:59:17 +00:00
|
|
|
set(QT_DEFAULT_MAJOR_VERSION 6)
|
2019-11-26 09:10:55 +00:00
|
|
|
include(src/corelib/Qt6CoreMacros.cmake)
|
|
|
|
|
2020-08-14 15:53:37 +00:00
|
|
|
# Needed when building qtbase for android.
|
|
|
|
include(src/corelib/Qt6AndroidMacros.cmake)
|
|
|
|
|
2020-10-02 13:38:47 +00:00
|
|
|
# Set up optimization flags like in qmake.
|
|
|
|
# This function must be called after the global QT_FEATURE_xxx variables have been set up,
|
|
|
|
# aka after QtBaseGlobalTargets is processed.
|
|
|
|
# It also has to be called /before/ adding add_subdirectory(src), so that per-directory
|
|
|
|
# modifications can still be applied if necessary (like in done in Core and Gui).
|
|
|
|
qt_internal_set_up_config_optimizations_like_in_qmake()
|
|
|
|
|
2019-09-19 07:38:09 +00:00
|
|
|
## Setup documentation
|
|
|
|
add_subdirectory(doc)
|
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
## Visit all the directories:
|
|
|
|
add_subdirectory(src)
|
|
|
|
endif()
|
2018-10-24 13:20:27 +00:00
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
if(BUILD_TESTING)
|
2018-10-24 13:20:27 +00:00
|
|
|
add_subdirectory(tests)
|
2019-11-04 13:43:39 +00:00
|
|
|
if(QT_NO_MAKE_TESTS)
|
|
|
|
set_property(DIRECTORY tests PROPERTY EXCLUDE_FROM_ALL TRUE)
|
|
|
|
endif()
|
2018-10-24 13:20:27 +00:00
|
|
|
endif()
|
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
if(NOT QT_BUILD_STANDALONE_TESTS)
|
|
|
|
if(QT_WILL_BUILD_TOOLS)
|
|
|
|
add_subdirectory(qmake)
|
|
|
|
endif()
|
|
|
|
# As long as we use the mkspecs (for qplatformdefs.h), we need to always
|
|
|
|
# install it, especially when cross-compiling.
|
2020-01-15 22:01:16 +00:00
|
|
|
set(mkspecs_install_dir "${INSTALL_MKSPECSDIR}")
|
2019-11-01 10:48:23 +00:00
|
|
|
qt_path_join(mkspecs_install_dir ${QT_INSTALL_DIR} ${mkspecs_install_dir})
|
|
|
|
|
2020-01-15 22:01:16 +00:00
|
|
|
file(GLOB mkspecs_subdirs
|
|
|
|
LIST_DIRECTORIES TRUE
|
|
|
|
"${PROJECT_SOURCE_DIR}/mkspecs/*")
|
2020-03-11 10:07:02 +00:00
|
|
|
foreach(entry IN LISTS mkspecs_subdirs)
|
|
|
|
if (IS_DIRECTORY ${entry})
|
|
|
|
qt_copy_or_install(DIRECTORY "${entry}"
|
2020-10-15 14:39:44 +00:00
|
|
|
DESTINATION ${mkspecs_install_dir}
|
|
|
|
USE_SOURCE_PERMISSIONS)
|
2020-03-11 10:07:02 +00:00
|
|
|
else()
|
|
|
|
qt_copy_or_install(FILES "${entry}"
|
|
|
|
DESTINATION ${mkspecs_install_dir})
|
|
|
|
endif()
|
2020-01-15 22:01:16 +00:00
|
|
|
endforeach()
|
2019-02-15 12:16:35 +00:00
|
|
|
endif()
|
2019-01-17 09:22:59 +00:00
|
|
|
|
2019-06-11 13:46:31 +00:00
|
|
|
qt_build_repo_end()
|
|
|
|
|
2019-11-01 10:48:23 +00:00
|
|
|
if(NOT QT_BUILD_STANDALONE_TESTS AND BUILD_EXAMPLES)
|
2019-01-17 09:22:59 +00:00
|
|
|
add_subdirectory(examples)
|
2019-11-04 13:43:39 +00:00
|
|
|
if(QT_NO_MAKE_EXAMPLES)
|
|
|
|
set_property(DIRECTORY examples PROPERTY EXCLUDE_FROM_ALL TRUE)
|
|
|
|
endif()
|
2019-01-17 09:22:59 +00:00
|
|
|
endif()
|