1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update start of cmake/README.md

Browse Source 
Make the document reflect the current status of the port.

Also link to https://doc.qt.io/qt-6/build-sources.html  and
https://wiki.qt.io/Building_Qt_6_from_Git as official sources
on how to build Qt. This document should IMO rather
concentrate on documenting the build system internals.

Change-Id: If62cb966b41b7452edb5b63725756916b66affac
Reviewed-by: Craig Scott <craig.scott@qt.io>
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from commit cf9683601857bb8ba0a5f24b13affa9de1e27ef8)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
Kai Köhne 2021-01-06 16:07:42 +01:00 committed by Qt Cherry-pick Bot
parent f193e7a793
commit 4b1153d1a2
1 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
cmake/README.md
View File

@ -1,20 +1,24 @@
# Status # Overview
Port is still on-going. This document gives an overview of the Qt 6 build system. For a hands-on guide on how
to build Qt 6, see https://doc.qt.io/qt-6/build-sources.html and
https://wiki.qt.io/Building_Qt_6_from_Git
Note: # CMake Versions
You need CMake 3.16.0 or later for most platforms (due to new AUTOMOC json feature).
You need CMake 3.17.0 to build Qt for iOS with the simulator_and_device feature.
You need CMake 3.17.0 + Ninja to build Qt in debug_and_release mode on Windows / Linux.
You need CMake 3.18.0 + Ninja to build Qt on macOS in debug_and_release mode when using frameworks.
# Intro * You need CMake 3.16.0 or later for most platforms (due to new AUTOMOC json feature).
* You need CMake 3.17.0 to build Qt for iOS with the simulator_and_device feature.
* You need CMake 3.17.0 + Ninja to build Qt in debug_and_release mode on Windows / Linux.
* You need CMake 3.18.0 + Ninja to build Qt on macOS in debug_and_release mode when using frameworks.
The CMake update offers an opportunity to revisit some topics that came up during the last few # Changes to Qt 5
years.
* The Qt build system does not support building host tools during a cross-compilation run. You need The build system of Qt 5 was done on top of qmake. Qt 6 is built with CMake.
to build a Qt for your host machine first and then use the platform tools from that version. The
This offered an opportunity to revisit other areas of the build system, too:
* The Qt 5 build system allowed to build host tools during a cross-compilation run. Qt 6 requires
you to build a Qt for your host machine first and then use the platform tools from that version. The
decision to do this was reached independent of cmake: This does save resources on build machines decision to do this was reached independent of cmake: This does save resources on build machines
as the host tools will only get built once. as the host tools will only get built once.
@ -24,14 +28,10 @@ years.
* There is less need for bootstrapping. Only moc and rcc (plus the lesser known tracegen and * There is less need for bootstrapping. Only moc and rcc (plus the lesser known tracegen and
qfloat16-tables) are linking against the bootstrap Qt library. Everything else can link against qfloat16-tables) are linking against the bootstrap Qt library. Everything else can link against
the full QtCore. This will include qmake. the full QtCore. This does include qmake.
Qmake is supported as a build system for applications *using* Qt going forward and will qmake is supported as a build system for applications *using* Qt going forward and will
not go away anytime soon. not go away anytime soon.
* We keep the qmake-based Qt build system working so that we do not interfere too much with ongoing
development.
# Building against homebrew on macOS # Building against homebrew on macOS
You may use brew to install dependencies needed to build QtBase. You may use brew to install dependencies needed to build QtBase.