Elias Toivola
574f06fdcc
Ubuntu 26.04 comes with GCC 15.2.0 and GNOME 50 which drops X11/xorg and
is Wayland only. X11 programs may run with XWayland within the Wayland
session.
The tier-1 -50 and -51 images are created and configured with Packer
instead of doing it manually. OS configurations can be checked at:
coin/pre-provisioning/qtci-linux-Ubuntu-26.04-x86_64/scripts/
coin/pre-provisioning/qtci-linux-Ubuntu-26.04-x86_64/http/user-data
Provisioning changes compared to x64 24.04:
- Pulseaudio backport is removed:
03-install-pulseaudio-16-bugfix-backports.sh
- 80-docker.sh is updated to noble -> resolute
- apt: python3-pypdf2 -> python3-pypdf
- '-snld20' param added to 7z commands
- 62-install-swiftly.sh: apt install swiftlang instead
- vx_works.sh: /etc/sysctl.conf -> /sysctl.d/ for net.ipv4.ip_forward=1
- 92-sbuild.sh: sbuild-update is deprecated -> comment out
- enable_test_stacktraces.sh: /usr/lib/sysctl.d/55-ptrace.conf for U26
[CI Platforms]
Pick-to: 6.12
Task-number: QTQAINFRA-8001
Task-number: QTQAINFRA-5844
Change-Id: Ic6951f46845f8de8ca012a7c4f353fb042a16ae4
Reviewed-by: Simo Fält <[email protected]>
Qt 6
This repository, qt5.git, is the Qt super-repository. It records a git
submodule pointer to each Qt module repository, such as qtbase and
qtdeclarative, along with the build system, the configure scripts, and the
continuous integration configuration that build those modules as a single tree.
Each submodule points at a specific revision. The combination of revisions that a branch records is a snapshot that has passed Qt's continuous integration. Clone this repository first and let it select the module revisions for you. If you move a submodule to a different revision, you are building a combination that nobody has tested.
Despite the name
qt5.git, thedevand6.xbranches contain Qt 6.
To use Qt rather than build it from sources, see Get and Install Qt.
Repository layout
Each Qt module lives in its own directory, such as qtbase or
qtdeclarative. Those directories are git submodules.
The other top-level entries are:
| Entry | Purpose |
|---|---|
.gitmodules |
Lists modules for the current branch. |
CMakeLists.txt |
Entry point for the top-level build of all modules. |
configure, configure.bat |
Wrappers that configure that build. |
init-repository |
Checks out the submodules. Git clones only. |
cmake/ |
CMake modules shared by the top-level build. |
coin/ |
Continuous integration configuration and provisioning. |
LICENSES/, REUSE.toml |
License texts and per-file licensing metadata. |
Get the sources
For instructions, see Getting Qt Sources from the Git repository.
Build Qt
For instructions, see Build from sources.
Documentation
The Qt 6 documentation covers the framework itself.
Report an issue
Report bugs at bugreports.qt.io, following these steps.
Security
To report a security vulnerability in Qt, and to read what the Qt Project commits to in response, see SECURITY.md.
Contribute to Qt
The Qt Project does not accept pull requests on GitHub. Every contribution goes through Gerrit, so read how to contribute before you push a change. All participation in the project is subject to our code of conduct. To learn who decides what, and how someone becomes an approver or a maintainer, see how the project is governed. Development discussions happens in the open on the Qt Project mailing lists.
License
Qt is available under both commercial and open source licenses, and the terms depend on the module you use. LICENSE explains how licensing is declared across the Qt repositories and where to find the terms that apply to a given module.
For the full picture, see the Qt licensing overview and qt.io/licensing.