What I want to use in a container deployed with Torizon OS:
- Commercial Qt 6.8.6 (LTS, 6.8.6 released Dec 2025)
- Applications developed in C++23 (decent supprt with GCC 14, but prefferably GCC 15, which is the latest stable release)
- Some recent distro (trixie has gcc-14, fine, forky (testing) would be ideal)
Toradex claims to have some kind of support for Debian feeds of commercial Qt, plus Qt themselves claim to provide feeds. But there is no single combination that satisfies my needs.
Cross-toolchain Torizon containers:
- stable-rc is still on bookworm
- next-rc is on trixie (even though trixie has been stable since Aug 2025).
Qt enterprise Debian packages:
- 6.8.6 – available for jammy (Ubuntu 22.04 LTS), but since jammy is extremely old by now, there are ABI incompatibilies if I try these packages on Trixie (e.g. libicu)
- 6.8.2 – this is what Torizon VS Code templates suggest/”support”, but they are not even compatible with Trixie due to gpgv → sqv changes, so this forces me into the stone age of Bookworm, where GCC 12 is way too old for C++23
So, whatever I choose, I am forced to either build something from source (be it Qt, the compiler, or both) or abandon Torizon OS all together and go back to Yocto BSP.
Can we please get more flexibility, fresher builds and fresher distro support? In particular:
- Forky Torizon images
- Qt feeds for Trixie, Forky etc.
- Reasonably patched Qt (like 6.8.6) built against all of them and not just e.g. jammy
Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
To help guide you properly, could you specify which hardware platform and OS version you’re using? For example:
Hardware examples:
- Verdin i.MX8M Plus
- Verdin AM62
- Aquila AM69
- Apalis i.MX8QP
- Colibri i.MX8X
OS examples:
- Torizon OS 6.8.2
- Torizon OS 7.2.0-build.13
- BSP 7.x.y
You can get this information by running the tdx-info command on your device. More details are available at: Getting Device Information with Tdx-Info | Toradex Developer Center
Current Qt Enterprise Support Status
Based on the available documentation, Qt Enterprise packages are currently only available for iMX8 devices(1). The Qt C++ Template for Torizon OS supports both Qt Open Source and Qt Enterprise licenses, automatically choosing based on the qt_license_login and qt_license_password settings(1).
Container Platform Information
The current Debian container matrix shows that Torizon OS 7 uses major 4 tags (such as torizon/debian-imx8:4), while Torizon OS 6 uses major 3 tags(2). The platform-specific containers available include variations for am62, am62p, imx8, imx95, and upstream platforms(2).
Once you provide your specific hardware and OS version details, I can give you more targeted guidance on the best approach for your Qt 6.8.6 and C++23 requirements within the current Torizon ecosystem.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
Greetings @vilchanskyio,
It would be difficult as of the time of writing to provide Qt enterprise packages for Trixie. This is because it seems Qt enterprise is only officially supported on Debian Bookworm: Enterprise Qt Debian Packages | Qt 6.11
Even on the latest version of Qt 6.11, the packages are only marked for Debian Bookworm. In theory one could try to use the Bookworm feeds on Trixie, but that would be some experimental work that would be difficult to actually support.
The first move would be for Qt to officially support Debian Trixie first, before we can proceed on our own side.
Did you see news somewhere that Qt officially supports Debian Trixie, or newer?
Best Regards,
Jeremias
Thanks for the reply.
Right, that confirmed my fears 
I asked Qt some time ago (about 3 months ago, via commercial support ticket) whether they plan to make feeds for newer distros, and the reply was that Qt 6.11 was already freezed. No idea about Qt 6.12, which should be the next LTS, if I’m not mistaken.
The fatal flaw of Qt’s “support” of Linux feeds is that the release cycle of Linux distros is different from the release cycle of Qt. For example, they do understand that this is a problem, because they address this in Yocto’s meta-qt6 and do support newer Yocto releases, as can be seen in the compat variable. In general, of course, it is much simpler in Yocto (usually a one-line change), than building and distributing N binaries accross M binary distros, but still.
The only lever that I see is that if we request a wider/more extended support. Otherwise, they will at most add support for Trixie in half a year (or when 6.12 is going to be) and that will be the status quo for another 4 years…
For compatibility and support reasons, we generally stick with what the vendor (Qt in this case) provides. Again it might be possible to “force” Qt enterprise to work on Debian Trixie. But, any issues would be difficult to support going forward, and Qt would most likely not provide us any support either as it goes outside of their official support.
This means the only practical options would be to wait fro official support from the Qt side. Or do the custom Yocto build, which of course would provide the greatest flexibility being able to customize essentially every aspect of the OS.
Best Regards,
Jeremias
