You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Qt V6.7.0 can be installed using the Qt online installer available from the Qt 6.7.0 release page [here][qt-online].
12
+
As an alternative, the Qt 6.7.0 offline installer can be used [here][qt-offline].
13
+
Packages for Windows and Linux are provided.
14
+
10
15
### Building on Windows
11
16
As a preliminary step, make sure that you have the following installed on your system:
12
17
* CMake 3.11 or above.
13
18
* Python 3.7 or above.
14
-
* Qt® 5 or above (5.15.2 is the default and recommended).
15
-
* Visual Studio® 2015 or above (2019 is the default).
19
+
* Qt® 6 or above (6.7.0 is the default and recommended).
20
+
* Visual Studio® 2019 or above (2022 is the default).
16
21
17
-
Qt V5.15.2 can be installed using the Qt online installer available from the Qt 5.15.2 release page [here][qt-online].
18
-
As an alternative, the Qt 5.12.6 offline installer can be used [here][qt-offline].
19
-
Qt should be installed to the default location (C:\Qt\Qt5.xx.x).
22
+
Qt should be installed to the default location (C:\Qt\Qt6.xx.x).
20
23
Be sure to select msvc2017/msvc2019 64-bit during Qt installation, depending on the compiler you decide to use.
24
+
Select msvc2019 if using Visual Studio 2022.
21
25
A reboot is required after Qt is installed.
22
26
23
27
CMake can be downloaded from [here](https://cmake.org/download/).
@@ -27,17 +31,19 @@ This can be installed once Python is installed, as follows:
27
31
* pip install -U sphinx
28
32
* pip install sphinx_rtd_theme
29
33
30
-
Run the python pre_build.py script in the build folder from a command prompt. If no command line options are provided, the defaults will be used (Qt 5.15.2 and Visual Studio 2019)
34
+
Run the python pre_build.py script in the build folder from a command prompt. If no command line options are provided, the defaults will be used (Qt 6.7.0 and Visual Studio 2022)
31
35
32
36
Some useful options of the pre_build.py script:
33
37
* --vs <VisualStudioversion>: generate the solution files for a specific Visual Studio version. For example, to target Visual Studio 2017, add --vs 2017 to the command.
34
38
* --qt <path>: full path to the folder from where you would like the Qt binaries to be retrieved. By default, CMake would try to auto-detect Qt on the system.
35
39
36
-
Once the script has finished, in the case of Visual Studio 2019, a sub-folder called 'vs2019' will be created containing the necessary build files.
37
-
Go into the 'vs2019' folder (build/win/vs2019) and double click on the RRA.sln file and build the 64-bit Debug and Release builds.
40
+
Once the script has finished, in the case of Visual Studio 2022, a sub-folder called 'vs2022' will be created containing the necessary build files.
41
+
Go into the 'vs2022' folder (build/win/vs2022) and double click on the RRA.sln file and build the 64-bit Debug and Release builds.
38
42
The Release and Debug builds of RRA will be available in the build/release and build/debug folders.
39
43
40
44
### Building on Ubuntu
45
+
If Qt is installed from a Qt installer, it should be installed to ~/Qt/Qt6.7.0 (the default of ~/Qt6.7.0 will not work).
46
+
41
47
Required dependencies can be installed as follows:
Qt V5.15.2 can be installed using the Qt online installer available from the Qt 5.15.2 release page [here][qt-online].
55
-
As an alternative, the Qt 5.12.6 offline installer can be used [here][qt-offline] (the .run file) and installed
56
-
to ~/Qt/Qt5.12.6 (the default of ~/Qt5.12.6 will not work).
57
61
58
-
XCB libraries are required for Qt v5.15.x (they are not needed for older Qt versions). By default, the CMake configuration will attempt to copy
59
-
these files from the Qt lib folder. If needed, the XCB library files (libxcb*) can be obtained from the /lib folder of the Radeon Developer Tool
60
-
Suite download found [here](https://gpuopen.com/tools/).
62
+
Qt6 can be installed from the package manager using:
63
+
```bash
64
+
sudo apt-get install qt6-base-dev
65
+
sudo apt-get install qt6-base-private-dev
66
+
```
67
+
As of this writing, this package on Ubuntu 2204 is 6.2.4
68
+
69
+
XCB libraries are required for Qt v5 and above. These can be installed by using:
70
+
```bash
71
+
sudo apt-get install libxcb-cursor-dev
72
+
```
61
73
62
74
Run the python pre_build.py in the build folder.
63
75
```bash
64
76
python3 pre_build.py
65
77
```
66
78
Or run the pre_build.py script with the -qt option to specify another version of Qt. For example:
67
79
```bash
68
-
python3 pre_build.py --qt 5.12.6
80
+
python3 pre_build.py --qt 6.7.0
69
81
```
70
82
The pre_build.py script will construct the output folders and build the necessary makefiles.
71
83
To build the release build, use:
@@ -81,25 +93,14 @@ Alternatively, building can be done directly from the prebuild script with the -
81
93
python3 pre_build.py --build
82
94
```
83
95
84
-
It is possible to use the system-installed version of Qt rather than using a Qt installer described above. At the time of this writing, Ubuntu 22.04 LTS
85
-
comes with Qt 5.15.3. To use the system Qt, a fake Qt package is needed. For Qt 5.15.3, this can be made by creating the required directory structure
96
+
If Qt is not installed from a Qt installer, a fake Qt package is needed. This can be made by creating the required directory structure
86
97
and setting up symbolic links to point to the system Qt lib and include directories:
Copy file name to clipboardExpand all lines: build/dependency_map.py
+2-3
Original file line number
Diff line number
Diff line change
@@ -22,13 +22,12 @@
22
22
# each git dependency has a desired directory where it will be cloned - along with a commit to checkout
23
23
# The third parameter in the value field is whether to do a shallow clone. Usually, this will be True but if a commit hash is used as a branch, a full clone is needed.
Copy file name to clipboardExpand all lines: build/pre_build.py
+13-6
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,11 @@
12
12
13
13
importos
14
14
importsys
15
+
importstat
15
16
importimportlib.util
16
17
importargparse
17
18
importshutil
18
19
importsubprocess
19
-
importdistutils.spawn
20
20
importplatform
21
21
importtime
22
22
@@ -63,9 +63,10 @@
63
63
else:
64
64
parser.add_argument("--qt-root", default="~/Qt", help="specify the root directory for locating QT on this system (default: ~/Qt) ")
65
65
parser.add_argument("--qt-system", action="store_true", help="use the system-installed version of QT")
66
-
parser.add_argument("--qt", default="5.15.2", help="specify the version of QT to be used with the script (default: 5.15.2)" )
66
+
parser.add_argument("--qt", default="6.7.0", help="specify the version of QT to be used with the script (default: 6.7.0)" )
67
67
parser.add_argument("--clean", action="store_true", help="delete any directories created by this script")
68
68
parser.add_argument("--no-qt", action="store_true", help="build a headless version (not applicable for all products)")
69
+
parser.add_argument("--build-number", default="0", help="specify the build number, primarily to be used by build machines to produce versioned builds")
69
70
parser.add_argument("--update", action="store_true", help="Force fetch_dependencies script to update all dependencies")
70
71
parser.add_argument("--output", default=output_root, help="specify the output location for generated cmake and build output files (default = OS specific subdirectory of location of pre_build.py script)")
71
72
parser.add_argument("--build", action="store_true", help="build all supported configurations on completion of prebuild step")
@@ -114,10 +115,10 @@ def mkdir_print(dir):
114
115
# Look for Qt path in specified Qt root directory
115
116
# Example:
116
117
# --qt-root=C:\\Qt
117
-
# --qt=5.15.2
118
-
# Look first for C:\\Qt\\Qt5.15.2\\5.15.2
118
+
# --qt=6.7.0
119
+
# Look first for C:\\Qt\\Qt6.7.0\\6.7.0
119
120
# (if not found..)
120
-
# Look next for C:\\Qt\\5.15.2
121
+
# Look next for C:\\Qt\\6.7.0
121
122
#
122
123
# If neither of those can be found AND we are using the default
123
124
# qt-root dir (i.e. the user did not specify --qt-root), then also
0 commit comments