It’s recommended to have ninja 1.8 or later installed.
For other platform specific requirements, please see section “Setting up your machine” on: http://wiki.qt.io/Get_The_Source
cd <path>/<source_package> ./configure -prefix $PWD/qtbase cmake --build .
cd <path>\<source_package> configure -prefix %CD%\qtbase cmake --build .
More details follow.
Qt is built with CMake, and a typical
configure && cmake --build . build process is
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.
The submodule repository
qtrepotools contains useful
scripts for developers and release engineers. Consider adding
qtrepotools/bin to your
PATH environment variable to access
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.
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
Information about Qt’s documentation is located in qtbase/doc/README
Note: Building the documentation is only tested on desktop platforms.