36fe46a392
The 'reuse' tool installed into the Python 3.8 environment on Windows has a broken 'jinja2' package, due to conan being installed after the sbom tool, which replaces the jinja package. pip reports the issue but does not actually exit with a non-zero status for some reason, thus not blocking the initial provisioning. The jinja2 version installed in the Python 3.10 environment on Windows is compatible with both conan and reuse. To work around the issue, explicitly install the sbom tools only for Python 3.10 on Windows platforms, and specify the path to the Python interpreter in an environment variable for the build system to use. Amends1f2fb6312cTask-number: QTBUG-122899 Task-number: QTBUG-124453 Task-number: QTBUG-125211 Change-Id: I386da17a1902dd26af332cef3482dbcb2221a1b3 Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io> Reviewed-by: Simo Fält <simo.falt@qt.io> (cherry picked from commite874a76a48) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
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.