On Dienstag, 3. Juni 2025 11:30:51 Mitteleuropäische Sommerzeit Ben Cooksley wrote: > On Tue, Jun 3, 2025 at 11:04 AM Lukas Sommer <sommer...@gmail.com> wrote: > > I have a question. Currently we have a static Windows Qt5 build, but we > > don't have a static windows Qt6 build, right? So when removing Qt5, there > > won't be any static windows build at all anymore? > > Unless someone does the work to look into what is needed to have Windows > static builds with Qt 6, that is correct. The changes needed may be rather > minimal. > I'm not entirely sure what is involved, and looking at the setup i'm not > sure if the builds are true static builds as I don't think we have a static > Qt build on Windows.
From what I remember the static Qt5 Windows job was just like its Linux counter-part only doing static builds of our stuff on top of a dynamic Qt. That catches some issues but doesn't result in something actually working, especially once (QML) plugins are involved. Those "semi-static" jobs were largely lost in the Qt6 migration, as nobody did the work to port them. We added an entirely new static Linux Qt 6 job though that actually uses a statically built Qt. That however exposed many more gaps in our support for static builds. And while we probably caught a lot of things also affecting Windows that way, it's likely more work than just a 1:1 port of the "semi- static" build to Qt6. Regards, Volker
signature.asc
Description: This is a digitally signed message part.
