blob: 205ff1d172eeab056dcd5fa627f772b4436bce81 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
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:
--------
1. Open a command prompt.
2. 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):
* `-release` Compile and link Qt with debugging turned off.
* `-debug` Compile 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.
|
