Qt6 + CMake migration #165

slipher · 2025-11-12T03:09:29Z

Requires the updater-wip branch from https://github.com/slipher/fluid.

There are two branches. This one, slipher/qt6, includes only the commits that are supposed to be related to Qt6 migration. The other one slipher/qt6-combined represents the actual working copy I am using which includes some other commits.

Upgrade from Qt 5.14 to 6.8; migrate from qmake to cmake; update Fluid by a lot which requires some migrations; also update Quazip which didn't require any migrations.

Current issues:

illwieckz · 2025-11-12T03:14:36Z

It now depends on libxcb-cursor.so.0 and I had to install libxcb-cursor0 on my end, meaning no one of the applications I use requires that, meaning that dependency is very rare.

Edit: I forgot to say I'm running Ubuntu 24.04.3 LTS Noble Numbat.

build-qt.sh

illwieckz · 2025-11-12T13:12:25Z

build-qt.sh

+    -DFEATURE_formlayout=OFF
+    -DFEATURE_fscompleter=OFF
+    -DFEATURE_future=OFF
+    -DFEATURE_gc_binaries=OFF


If this is the same as -gc-binaries, it should be ON to reduce size:

According to https://doc.qt.io/qt-6/build-optimized-qt.html:

-gc-binaries
Remove unnecessary parts from binary. Place each function or data item into its own section and enable linker garbage collection of unused sections.

Done. gc-binaries + reduce-exports shaved off 1.8M.

illwieckz · 2025-11-12T14:25:17Z

I get this:

In file included from /updater/downloadworker.cpp:20:
/updater/downloadworker.h:25:10: fatal error: QStandardItemModel: No such file or directory
   25 | #include <QStandardItemModel>
      |          ^~~~~~~~~~~~~~~~~~~~

slipher · 2025-11-12T14:57:27Z

I get this:

In file included from /updater/downloadworker.cpp:20:
/updater/downloadworker.h:25:10: fatal error: QStandardItemModel: No such file or directory
   25 | #include <QStandardItemModel>
      |          ^~~~~~~~~~~~~~~~~~~~

I guess the "remove an unused include" commit from slipher/qt6-combined is needed.

illwieckz · 2025-11-12T15:15:15Z

That was that, thanks!

illwieckz · 2025-11-12T15:30:40Z

Out of curiosity, I tried building Qt without OpenGL, to see if that would save space. The updater builds and runs this way but that looks ugly: curves are aliased, and some background color on configuration dialog is wrong.

illwieckz · 2025-11-12T15:46:07Z

It now depends on libxcb-cursor.so.0 and I had to install libxcb-cursor0 on my end, meaning no one of the applications I use requires that, meaning that dependency is very rare.

Edit: I forgot to say I'm running Ubuntu 24.04.3 LTS Noble Numbat.

That's annoying: when that dependency isn't there, Qt6 doesn't build, but we cannot ship an updater requiring it.

On Ubuntu 24.04 that dependency is not installed by default, and is required by only 8 softwares! That means no one have this dependency installed on Ubuntu LTS! Maybe we will have to build it statically.

slipher · 2025-11-12T16:05:01Z

Out of curiosity, I tried building Qt without OpenGL, to see if that would save space. The updater builds and runs this way but that looks ugly: curves are aliased, and some background color on configuration dialog is wrong.

The Qt Quick documentation says that some effects are expected not to display if software rendering is used. Also I get high CPU usage in that mode (for me it happens when I run the app from a container that lacks some support libs).

It now depends on libxcb-cursor.so.0 and I had to install libxcb-cursor0 on my end, meaning no one of the applications I use requires that, meaning that dependency is very rare.
Edit: I forgot to say I'm running Ubuntu 24.04.3 LTS Noble Numbat.

That's annoying: when that dependency isn't there, Qt6 doesn't build, but we cannot ship an updater requiring it.

On Ubuntu 24.04 that dependency is not installed by default, and is required by only 8 softwares! That means no one have this dependency installed on Ubuntu LTS! Maybe we will have to build it statically.

Ouch. It seems Qt 6 has the opposite problem of Qt 5, which had too few hard requirements and ended up not displaying properly on the initial attempt to upgrade to Bullseye. There is an extensive list of libs for the test named xcb_syslibs in the build system which are required all or nothing. But recently I saw somewhere an option for using an internal xcb that we should try out. I forgot what the option is called but I can see the code in there at qtbase src/3rdparty/xcb/.

slipher · 2025-11-14T02:31:49Z

I now have a version that statically links against the libxcb-XXX libraries from Debian.

illwieckz · 2025-11-14T02:39:05Z

Excellent!

illwieckz · 2025-11-14T02:52:30Z

Some minor changes that live in a local branch of mine:

The install command looks like this way on my end:

RUN apt-get update \
    && apt-get install -y \
    autoconf \
    autopoint \
    ca-certificates \
    curl \
    gettext \
    git \
    g++ \
    libgl1-mesa-dev \
    libtool \
    libx11-xcb-dev \
    libxcb-glx0-dev \
    libxkbcommon-x11-dev \
    make \
    ninja-build \
    perl \
    p7zip-full \
    pkg-config \
    python \
    xz-utils \
    zlib1g-dev \
    $XCB_MINIMUM_PACKAGES \
    && echo 'deb https://archive.debian.org/debian bullseye-backports main' > /etc/apt/sources.list.d/backports.list \
    && apt-get update \
    && apt-get install -y \
    cmake/bullseye-backports \
    && apt-get clean

It installs explicitely ca-certificates because that's needed for the archive depot. It worked before because a package pulled it (probably curl), but it's not bad to be explicit.
It runs apt-get clean at the end in hope the snapshotted docker step is smaller on disk.
The backport repository url is made a bit smaller.
Also, just as a style concern, I put the && at the beginning of the line so it makes more obvious to my eyes it's a command and not an argument.

I also have a patch that moves the Aria build before the Qt build, so anytime Qt changes are made, the whole build is faster because modifying the Qt build doesn't invalidate the Aria build because of ordering.

I had a third patch adding ENV LANG=C.UTF-8 before anything else, but you already implemented the same yourself.

illwieckz · 2025-11-14T03:27:13Z

I don't know if that's bad or not, but Qt links against libxcb-xkb.a while also linking against libxkbcommon-x11.so.0 which is linked against libxcb-xkb.so.1, meaning we link against two libxcb-xkb, and one of them will be the static one from the Debian docker, while the other one will be the shared one from the user's computer.

illwieckz · 2025-11-14T04:10:38Z

Doing this makes sure the shared lib is always used for xcb-xkb while others are linked statically:

RUN ls /usr/lib/x86_64-linux-gnu/libxcb-*.so | grep -v xcb-xkb | xargs rm -v

slipher · 2025-11-14T04:12:23Z

The input part is where Qt has a bundled one that we can try. -qt-xkb or something in the configure args

illwieckz · 2025-11-14T11:53:04Z

The backports list file was removed:

E: Release 'bullseye-backports' for 'cmake' was not found

Also I noticed the backport url could use http, making it possible to be fetched before installing ca-certificates. Debian does it own crypto thing and doesn't need to trust the carrier as it can validate the package whatever the way it was sourced. This makes possible to do a single apt update.

That ca-certificates package is likely needed for the curl download, but then keeping it implicit from curl now sounds fine.

That's doable:

RUN echo 'deb http://archive.debian.org/debian bullseye-backports main' > /etc/apt/sources.list.d/backports.list \
    && apt-get update \
    && apt-get install -y \
    autoconf \
    autopoint \
    curl \
    gettext \
    git \
    g++ \
    libgl1-mesa-dev \
    libtool \
    libx11-xcb-dev \
    libxcb-glx0-dev \
    libxkbcommon-x11-dev \
    make \
    ninja-build \
    perl \
    p7zip-full \
    pkg-config \
    python \
    xz-utils \
    zlib1g-dev \
    $XCB_MINIMUM_PACKAGES \
    && apt-get install -y \
    cmake/bullseye-backports \
    && apt-get clean

illwieckz · 2025-11-16T23:19:35Z

The commit spam no-pie/no-pic mistakenly deletes this line from the OpenSSL build:

RUN ./config --prefix=/openssl --openssldir=/dev/null no-shared no-apps no-autoload-config no-capieng no-dso no-dynamic-engine no-engine no-loadereng no-module -Os

illwieckz · 2025-11-17T00:18:19Z

Dockerfile

+# Note: {foo:+bar} here is a syntax of the Dockerfile, not the shell!
+ENV IPO_ARG=${release:+-DCMAKE_INTERPROCEDURAL_OPTIMIZATION=ON}
+RUN echo IPO_ARG ${IPO_ARG}
+RUN BUILDQT_CMAKE_ARGS="${IPO_ARG} -DCMAKE_POSITION_INDEPENDENT_CODE=OFF -DFEATURE_reduce_relocations=OFF" CXXFLAGS='-fno-pic -no-pie' CFLAGS='-fno-pic -no-pie' PKG_CONFIG_PATH=/openssl/lib64/pkgconfig ./build-qt.sh && mv qt /qt && rm -rf /build-qt


-DCMAKE_POSITION_INDEPENDENT_CODE=OFF ${IPO_ARG} instead of ${IPO_ARG} -DCMAKE_POSITION_INDEPENDENT_CODE=OFF

What's the difference?

${IPO_ARG} -DCMAKE_POSITION_INDEPENDENT_CODE=OFF always disable IPO.

slipher · 2025-11-17T02:03:58Z

The commit spam no-pie/no-pic mistakenly deletes this line from the OpenSSL build:
RUN ./config --prefix=/openssl --openssldir=/dev/null no-shared no-apps no-autoload-config no-capieng no-dso no-dynamic-engine no-engine no-loadereng no-module -Os

Fixed

slipher · 2025-11-18T13:03:54Z

There is now a Windows build, which seems to work in non-release mode. (But if you pass release=1, you get an internal compiler error.)

slipher · 2025-11-20T05:03:16Z

Fixed issue with the app not exiting when all windows are closed.

Also added the toolchain file for MinGW which I forgot to add before.

illwieckz · 2025-11-20T05:19:23Z

Fixed issue with the app not exiting when all windows are closed.

Thanks a lot!

also switch to ninja

Will be needed for Qt 6 since the Bullseye mingw gcc is too old (no <future>). Anyway there is no reason not to use the newest compiler for Windows builds.

Now the submodule ref can be used as-is Clean up some Fluid hackiness.

slipher · 2025-11-28T03:57:55Z

Finally got the modal dialog thing. Turns out it is not implemented for "non-native" dialogs until Qt 6.10. The Debian distro libraries used "native" dialogs so that's why the problem could not be reproduced there. I tried building with version 6.10 but then the dialog wouldn't open at all. So I backported the commit to 6.8.

Something that is broken is the render of the “Continue reading” link, the HTML code explicitly says this should be cyan and aligned to the right, while it is rendered as white and aligned to the left. Actually that look isn't that bad, and we may decide to do it purposely, but that's not what the code is asking for.

Fixed

illwieckz · 2025-11-28T06:21:37Z

You may be interested in my build-qt: per-module patch application patch to simplifies the application of patches, this is something I wrote when I added a patch for qtshadertools but I rebased it and rewrote it to be even more generic so it could handle without custom code the qtdeclarative patch you added.

illwieckz · 2025-11-28T06:23:28Z

I see no difference with “Continue reading”.

slipher · 2025-11-28T13:20:40Z

Maybe it would be better to just test slipher/qt6-combined since I keep forgetting to update the slipher/qt6 pointer.

slipher · 2025-11-28T13:22:19Z

Maybe it would be better to just test slipher/qt6-combined since I keep forgetting to update the slipher/qt6 pointer.

Never mind, I don't think it was in there either. Pushed both

illwieckz · 2025-11-28T22:42:34Z

This is starting to look (the PR) very good!

illwieckz · 2025-12-03T04:02:09Z

About fontconfig support, I noticed we require it on Linux to be able to render the names of the user's folders in the install directory picker window.

We not only have to render our blog posts, we also have to render any character in a file path on user's computers.

illwieckz · 2025-12-03T09:02:47Z

Another regression spotted: when we hover the “Continue reading” link, the mouse pointer doesn't turn into a finger pointing hand.

illwieckz reviewed Nov 12, 2025

View reviewed changes

build-qt.sh Outdated Show resolved Hide resolved

illwieckz reviewed Nov 12, 2025

View reviewed changes

slipher force-pushed the slipher/qt6 branch from c812e31 to 0ec3df1 Compare November 13, 2025 02:58

illwieckz mentioned this pull request Nov 14, 2025

Things to do to reduce the executable binary size #164

Open

6 tasks

slipher force-pushed the slipher/qt6 branch 3 times, most recently from aa400d7 to 780eba1 Compare November 16, 2025 13:36

illwieckz reviewed Nov 17, 2025

View reviewed changes

slipher force-pushed the slipher/qt6 branch from 780eba1 to ab9f023 Compare November 17, 2025 02:03

slipher force-pushed the slipher/qt6 branch from 787e06b to 1c42103 Compare November 20, 2025 05:01

slipher force-pushed the slipher/qt6 branch from 1c42103 to f5094a0 Compare November 21, 2025 13:26

slipher added 20 commits November 27, 2025 21:31

[squashme]WIP: Qt6 + CMake + Fluid + Quazip upgrade

f688cc2

[squashme]Switch to qt_add_qml_module (requires newer cmake)

ad45906

[squashme]Improve Qt + Linux Docker builds

082a0ed

[squashme]clean up build-qt.sh

4120cba

[squashme]binary size reducing flags

f2792bb

[squashme]static link xcb-* libs from debian

e345156

[squashme]make compression on by default for rcc

a97d2ca

[squashme]apt cleanup from illwieckz

492cfa6

[squashme]Use cmake IPO with 'release' arg

3ff9dcd

also switch to ninja

[squashme]spam no-pie/no-pic

ac2ba05

[squashme]cleanup

1dc5256

[squashme]Windows Docker build - bump Debian bullseye -> trixie

641ad70

Will be needed for Qt 6 since the Bullseye mingw gcc is too old (no <future>). Anyway there is no reason not to use the newest compiler for Windows builds.

[squashme]Windows build

3fb787e

[squashme]disconnected news fix

cfee93c

[squashme]Use customized cmake for Fluid

5e58ac4

Now the submodule ref can be used as-is Clean up some Fluid hackiness.

[squashme]Restore text editing functionality

5942baa

[squashme] disable xkb x11 extension

9a471c2

[squashme] fix folder dialog warning spam

26f1edb

[squashme]no sed separate stream

95eacee

[squashme] backport dialog modalness implementation from 6.10

4e4079a

slipher force-pushed the slipher/qt6 branch from c7cbcea to 4e4079a Compare November 28, 2025 03:38

[squashme] reenable css parser - fixes "continue reading"

0a8f417

Qt6 + CMake migration #165

Are you sure you want to change the base?

Qt6 + CMake migration #165

Uh oh!

Conversation

slipher commented Nov 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

illwieckz commented Nov 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

illwieckz Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

slipher Nov 13, 2025

Choose a reason for hiding this comment

Uh oh!

illwieckz commented Nov 12, 2025

Uh oh!

slipher commented Nov 12, 2025

Uh oh!

illwieckz commented Nov 12, 2025

Uh oh!

illwieckz commented Nov 12, 2025

Uh oh!

illwieckz commented Nov 12, 2025

Uh oh!

slipher commented Nov 12, 2025

Uh oh!

slipher commented Nov 14, 2025

Uh oh!

illwieckz commented Nov 14, 2025

Uh oh!

illwieckz commented Nov 14, 2025

Uh oh!

illwieckz commented Nov 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

illwieckz commented Nov 14, 2025

Uh oh!

slipher commented Nov 14, 2025

Uh oh!

illwieckz commented Nov 14, 2025

Uh oh!

illwieckz commented Nov 16, 2025

Uh oh!

illwieckz Nov 17, 2025

Choose a reason for hiding this comment

Uh oh!

slipher Nov 17, 2025

Choose a reason for hiding this comment

Uh oh!

illwieckz Nov 17, 2025

Choose a reason for hiding this comment

Uh oh!

slipher commented Nov 17, 2025

Uh oh!

slipher commented Nov 18, 2025

Uh oh!

slipher commented Nov 20, 2025

Uh oh!

illwieckz commented Nov 20, 2025

Uh oh!

slipher commented Nov 28, 2025

Uh oh!

illwieckz commented Nov 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

illwieckz commented Nov 28, 2025

Uh oh!

slipher commented Nov 28, 2025

Uh oh!

slipher commented Nov 28, 2025

Uh oh!

illwieckz commented Nov 28, 2025

Uh oh!

illwieckz commented Dec 3, 2025

Uh oh!

illwieckz commented Dec 3, 2025

slipher commented Nov 12, 2025 •

edited

Loading

illwieckz commented Nov 12, 2025 •

edited

Loading

illwieckz commented Nov 14, 2025 •

edited

Loading

illwieckz commented Nov 28, 2025 •

edited

Loading