30aadf11aa
This commit adds size-optimized Qt configuration for Qt Quick apps. By having a CI configuration helps in ensuring that the configuration doesn't break over time. The goal of the configurations is to provide a size-optimized build while typical Quick applications should still work. The latter point was checked by checking several example apps: Coffeemachine, Calqlatr, Gallery, Colorpalette, and few smaller test applications. Space-savings are in 60% ballpark when comparing optimized with non-optimized static builds. Optimizations also include stripping the binaries where applicable. Tested platforms: iOS, macOS, Windows, Linux, WebAssembly and Android. Autotests are compiled and run only on one platform (macOS) to preserve CI compute. Configurations are 'Insignificant' to avoid interruptions - this should be changed once proven stable. Notably all except Android builds are static builds; static build optimizations (LTO in particular) are very powerful in optimizing size. Qt for Android OTOH does not support static builds. There are more features and options that user can disable for further space savings. Prior art for Linux show-cases taking the optimizations further (QTBUG-117638). This commit is preceded by numerous compilation fixes to qtbase and qtdeclarative (now merged). Fixes: QTBUG-134299 Change-Id: Iaec0aea3e9d475220161ca8d00f0ec15eaa637a9 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io> Reviewed-by: Simo Fält <simo.falt@qt.io>
HOW TO BUILD Qt 6
Synopsis
System requirements
- C++ compiler supporting the C++17 standard
- CMake
- Ninja
- Python 3
For more details, see also https://doc.qt.io/qt-6/build-sources.html
Linux, Mac:
cd <path>/<source_package>
./configure -prefix $PWD/qtbase
cmake --build .
Windows:
- Open a command prompt.
- Ensure that the following tools can be found in the path:
- Supported compiler (Visual Studio 2022 or later, or MinGW-builds gcc 13.1 or later)
- Python 3 ([https://www.python.org/downloads/windows/] or from Microsoft Store)
cd <path>\<source_package>
configure -prefix %CD%\qtbase
cmake --build .
More details follow.
Build!
Qt is built with CMake, and a typical
configure && cmake --build . build process is used.
If Ninja is installed, it is automatically chosen as CMake generator.
Some relevant configure options (see configure -help):
-releaseCompile and link Qt with debugging turned off.-debugCompile and link Qt with debugging turned on.
Example for a release build:
./configure -prefix $PWD/qtbase
cmake --build .
Example for a developer build: (enables more autotests, builds debug version of libraries, ...)
./configure -developer-build
cmake --build .
See output of ./configure -help for documentation on various options to
configure.
The above examples will build whatever Qt modules have been enabled by default in the build system.
It is possible to build selected repositories with their dependencies by doing
a ninja <repo-name>/all. For example, to build only qtdeclarative,
and the modules it depends on:
./configure
ninja qtdeclarative/all
This can save a lot of time if you are only interested in a subset of Qt.
Hints
The submodule repository qtrepotools contains useful scripts for
developers and release engineers. Consider adding qtrepotools/bin
to your PATH environment variable to access them.
Building Qt from git
See http://wiki.qt.io/Building_Qt_6_from_Git and README.git for more information. See http://wiki.qt.io/Qt_6 for the reference platforms.
Documentation
After configuring and compiling Qt, building the documentation is possible by running
cmake --build . --target docs
After having built the documentation, you need to install it with the following command:
cmake --build . --target install_docs
The documentation is installed in the path specified with the
configure argument -docdir.
Information about Qt's documentation is located in qtbase/doc/README
Note: Building the documentation is only tested on desktop platforms.