Skip to content

Update from QT5.15 to QT6.10.2#293

Merged
spham-amzn merged 4 commits intomainfrom
qt6
Feb 13, 2026
Merged

Update from QT5.15 to QT6.10.2#293
spham-amzn merged 4 commits intomainfrom
qt6

Conversation

@guillaume-haerinck
Copy link
Contributor

@guillaume-haerinck guillaume-haerinck commented Sep 23, 2025

What does this PR do?

Upgrade the QT library version to QT6.10.2. This works in conjonction with the O3DE Qt6 branch.

What changes from vanilla QT ?

Nothing, we are using vanilla QT. In the process, we are nuking the custom changes listed below which were previously used.

Repo O3DE Fork Changes outline
QImageFormats compare - Advanced support for TIFF file format
QBase compare - New PropagateStyleToChildren flag
- New ManualStyleSheet flag
- Styling rendering optimization
- Advanced layouting for tooltips
- MacOS ssl changes
- Tree view expand behavior changes
Qt5 compare - Update QT git modules to point to fork when required

How to test ?

Prerequisites are the same as building o3de from source. It is also recommended to delete your previous build folder to prevent symbols mismatch.

You will likely want to build the editor with a target project, you can use the LY_PROJECTS flag in cmake configure to point to one of your o3de project.

(from your cloned o3de source repository)
mkdir build
cd build
cmake .. -DLY_PROJECTS=PATH_TO_YOUR_PROJECT

On Windows

  • Download build artifacts from this PR. On windows it is currently this link (you need to be connected to github)
  • Extract the zip file and copy qt-6.10.2-rev1-windows.tar.xz in C:\Users\YOUR_USER_NAME\.o3de\3rdParty\downloaded_packages
  • On your O3DE repository, checkout the QT6 branch
  • Configure the project with cmake and build Editor target
    • If you run into an issue with package not found, have a look at BuiltInPackages to update the QT6 package hash to match what is in the zip file qt-6.10.2-rev1-windows.tar.xz.SHA256SUMS

On Linux

You must have libicu70 (can be downloaded from https://pkgs.org/search/?q=libicu70).

  • Download build artifacts from this PR. On ubuntu it is currently this link (you need to be connected to github)
  • Extract the zip file and copy qt-6.10.2-rev1-linux.tar.xz in YOUR_USER_NAME/.o3de/3rdParty/downloaded_packages
  • On your O3DE repository, checkout the QT6 branch
  • Configure the project with cmake and build Editor target
    • If you run into an issue with package not found, have a look at BuiltInPackages to update the QT6 package hash to match what is in the zip file qt-6.10.1-rev2-linux.tar.xz.SHA256SUMS
mkdir build
cd build
cmake .. -DLY_PROJECTS=PATH_TO_YOUR_PROJECT
cmake --build . -j 8 --target Editor
./build/bin/profile/Editor --project-path=YOUR_PROJECT_PATH

** For Wayland **

If you want to make wayland work, these files will be of interest :

  • YOUR_USER_NAME/.o3de/3rdParty/packages/qt-6.8.3-rev2-linux/FindQt.cmake and the Platform folder
  • Code\Editor\Platform\Linux\Editor\Core\QtEditorApplication_linux.cpp

@guillaume-haerinck guillaume-haerinck added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 18, 2025
@guillaume-haerinck guillaume-haerinck force-pushed the qt6 branch 2 times, most recently from 0b2c094 to 78cb5fc Compare October 19, 2025 11:28
@yaakuro
Copy link

yaakuro commented Nov 9, 2025

As described above, I was also getting libicui18n.so.70: cannot open shared object ....
To fix this issue on my end, I just ran:

wget https://launchpad.net/ubuntu/+source/icu/70.1-2/+build/23145450/+files/libicu70_70.1-2_amd64.deb
sudo dpkg -i libicu70_70.1-2_amd64.deb

@nick-l-o3de
Copy link
Contributor

I tested this on windows, and with the given rev1 pack, I didn't encounter any issues in the following

  • Editor
    • any editor sub tools (input bindings, animation editor, particle editor, etc)
  • Assetbundler - (minor checkbox alignment thing)
  • LuaIDE
  • MaterialEditor
  • MaterialCanvas
  • AssetProcessor

@guillaume-haerinck guillaume-haerinck changed the title Update from QT5.15 to QT6.8.3 Update from QT5.15 to QT6.10.1 Jan 23, 2026
"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe" modify --installPath "C:\Program Files\Microsoft Visual Studio\2022\Enterprise" --add Microsoft.VisualStudio.Component.VC.14.29.16.11.x86.x64 --add Microsoft.VisualStudio.Component.VC.14.29.16.11.ATL --add Microsoft.VisualStudio.Component.VC.14.29.16.11.CLI.Support --quiet --norestart

- name: Update msbuild path
if: runner.os == 'Windows'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Required as QT6 needs at least vs2022, not 2019

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to know. We'll be updating requirements for VS2022

@guillaume-haerinck guillaume-haerinck force-pushed the qt6 branch 2 times, most recently from b3b8802 to e0967d2 Compare January 31, 2026 21:16
@guillaume-haerinck guillaume-haerinck removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 31, 2026
@guillaume-haerinck guillaume-haerinck changed the title Update from QT5.15 to QT6.10.1 Update from QT5.15 to QT6.10.2 Jan 31, 2026
@guillaume-haerinck guillaume-haerinck requested review from a team and nick-l-o3de January 31, 2026 21:45
@guillaume-haerinck guillaume-haerinck force-pushed the qt6 branch 5 times, most recently from e0f4c58 to d7dcb87 Compare February 2, 2026 07:19
Signed-off-by: guillaume-haerinck <guillaume.haerinck@outlook.com>
Signed-off-by: guillaume-haerinck <guillaume.haerinck@outlook.com>
Signed-off-by: guillaume-haerinck <guillaume.haerinck@outlook.com>
Signed-off-by: Steve Pham <82231385+spham-amzn@users.noreply.github.com>
Co-authored-by: guillaume-haerinck <guillaume.haerinck@outlook.com>
Add xcb support

Signed-off-by: Steve Pham <82231385+spham-amzn@users.noreply.github.com>
Copy link
Contributor

@amzn-changml amzn-changml left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe" modify --installPath "C:\Program Files\Microsoft Visual Studio\2022\Enterprise" --add Microsoft.VisualStudio.Component.VC.14.29.16.11.x86.x64 --add Microsoft.VisualStudio.Component.VC.14.29.16.11.ATL --add Microsoft.VisualStudio.Component.VC.14.29.16.11.CLI.Support --quiet --norestart

- name: Update msbuild path
if: runner.os == 'Windows'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to know. We'll be updating requirements for VS2022

@spham-amzn spham-amzn merged commit 694932d into main Feb 13, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants