# Building Qt 6 from Git

En Ar Bg De El Es Fa Fi Fr Hi Hu It Ja Kn Ko Ms Nl Pl Pt Ru Sq Th Tr Uk Zh

This article provides hints for checking out and building the Qt 6 repositories. This is primarily for developers who want to contribute to the Qt library itself, or who want to try the latest unreleased code.

If you simply want to build a specific release of Qt from source to use the libraries in your own project, you can download the source code from the Official Releases page or the Archive. Alternatively, commercial customers can download the Source Packages via the Qt Account portal.

To compile Qt Creator, see Building Qt Creator from Git.

To compile Qt 5, see Building Qt 5 from Git

## System Requirements

### All desktop platforms

• Git (>= 1.6.x)
• CMake (>= 3.16, >= 3.18.4 for Ninja Multi-Config)
• Ninja
• Perl (>=5.14)
• Python (>=2.6.x)
• A working C++ compiler, supporting at least C++ 17

## Getting the source code

First clone the top-level Qt git repository:

$git clone git://code.qt.io/qt/qt5.git  or (if you're behind a firewall and want to use the https protocol): $ git clone https://code.qt.io/qt/qt5.git


Do not worry about the name mentioning qt5.git. This is also used for Qt 6.

Then check out the target branch (see Branch Guidelines). Currently, the only branch that exists for Qt 6 is dev, but in the future this will change, allowing to e.g. check out sources from 6.0

$cd qt5$ git checkout 6.0


### Getting the submodule source code

As described in the README.git, initialize the repository using the init-repository script, which clones the various sub-modules of Qt 6.

$cd qt5$ perl init-repository


In order to build a specific release of Qt, you can checkout the desired tag:

$cd qt5$ git checkout v6.0.0-beta4
$perl init-repository  ## Configuring and Building Qt 6 is built with CMake, and can be configured also by just running cmake with appropriate options. We provide some convenience scripts though that makes configuring Qt, and individual Qt modules easier. A build script called configure (or configure.bat for Windows) will be in the directory that you git cloned the source code into (~/qt5 if you followed the directions above). You will want to call that script from a different, parallel-level directory, because you do not want to build Qt in the directory that holds the source code. Instead, you should use a "shadow build", meaning you should not build into the source directory. $ mkdir qt6-build
$cd qt6-build$ ../qt5/configure -prefix /path/to/install
$cmake --build . --parallel 4$ cmake --install .


Where 4 is number of jobs. You can try your own value or use auto value using --parallel without argument.

On Windows:

> mkdir qt6-build
> cd qt6-build
> ..\qt5\configure.bat -prefix C:\path\to\install
> cmake --build .
> cmake --install .


Run configure -help to get an overview of available options.

You can also pass CMake options directly to configure:

 > ../qt5/configure -- -D QT_NO_BUILD_TESTS=ON


### Developer Builds

The configure option -developer-build sets the install prefix to the build directory, so that no install step is necessary. It also changes defaults so that all tests (including tests using private API that is otherwise not exported) can run.

This can take quite some time though. If you do want to be able to build the tests, but only on request, configure with CMake variable QT_BUILD_TESTS_BY_DEFAULT=OFF:

 $../qt5/configure -developer-build -- -D QT_BUILD_TESTS_BY_DEFAULT=OFF$ cmake --build . --parallel


Later on you can then build single tests, for instance :

 $cmake --build . --target tst_qstyle  Use ninja -t targets to see all the targets that are provided in the build. See cmake/README.md in the sources for details on how to configure and build Qt 6 with CMake. ### Running Tests Once you've built (as long as you you did build with tests enabled), you can run the tests either directly using ninja tst_qlocale_check (for example, to run tests/auto/corelib/text/qlocale/tst_qlocale) or via ctest (see its man page for further options) like $ ctest -V -R qlocale


(for the same example); the parameter to -R is a regular expression, matching test names. This includes the test output; if you omit -V that's skipped and you just get a single-line summary of the test result.