0055441fc7
Currently any configuration tagged with the 'LicenseCheck' feature uses the qtqa/master tst_licenses.pl script for license checking. The exact instructions that are run are hard-coded in the Coin repository. This is inflexible, and also confusing because qtqa has a dev and a master branch, and people forget to cherry-pick changes to the master branch. Furthermore always using the qtqa/master branch for all qt5.git branches is limiting, because no instruction changes can be made to a specific qt5.git branch. Using the new instructions added in qtbase commit 2a0e89981a52633c497f62bad0c7d26c466493cb we can now tag configurations with the 'LicenseCheckV2' feature. Integrations will then use the instructions from the active qtbase SHA1 to run the license check. Currently the qtbase instructions will always use the qtqa/dev branch for the license check, for both the dev and 6.8 branches, but in the near future we will likely want to create versioned branches for the qtqa repo, just like the rest of our repositories, so that we can have specific license check instructions for specific branches. Pick-to: 6.8 Task-number: QTBUG-124453 Task-number: QTBUG-125211 Task-number: QTBUG-125569 Task-number: QTQAINFRA-3935 Change-Id: Ica024dec44a9581c49cdfb555ba93667f7b34780 Reviewed-by: Toni Saario <toni.saario@qt.io> Reviewed-by: Lucie Gerard <lucie.gerard@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 2019 or later, or MinGW-builds gcc 11.2 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.