bead5e8720
New cmake_platforms_static_tests.yaml file will be included in repos that support building and running a minimal subset of tests built against a static Qt. Currently it's limited to qtbase. Moved existing 'linux-SLES static' config into this new file and also added a macOS and Windows config. Skipped specifying the PostgreSQL lib path for Windows and macOS because the plugin gets automatically linked into tst_moc, but the test build phase doesn't actually call find_package for PostgreSQL and the build system generation fails. Similary skipped specifying the openssl lib location for macOS, because the module_includes cmake auto test fails to find the WrapOpenSSLHeaders package. Explicitly tag iOS static config with DisableTests. The instructions already skipped building tests for iOS, but it's better to be explicit and update the instructions not to do that anymore. Pick-to: 6.1 Task-number: QTBUG-87580 Change-Id: I0d38a0ad055c92646609202691aeb8db29689f5a Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
HOW TO BUILD Qt6
Synopsis
System requirements
- CMake 3.18 or later
- Perl 5.8 or later
- Python 2.7 or later
- C++ compiler supporting the C++17 standard
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
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 8.1 or later)
- Perl version 5.12 or later [http://www.activestate.com/activeperl/]
- Python version 2.7 or later [http://www.activestate.com/activepython/]
- Ruby version 1.9.3 or later [http://rubyinstaller.org/]
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 /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.