3 ms·
>Today if I use Qt I don't bother with the official SDK on any platform, as it's not really worth it. Like, what, do I need to pipe my Qt account credentials in
by fluoridation 3y ago
>Today if I use Qt I don't bother with the official SDK on any platform, as it's not really worth it. Like, what, do I need to pipe my Qt account credentials into CI? No thanks, I'll build it myself.
On Windows you can just run the installer and then copy the installation directory from one computer to another. I think it doesn't even touch PATH.
- jchw 3y agoYeah, but that's not really great for CI purposes. I want to have a good "source of truth" for binaries somewhere, and needing an account to update those binaries is unnecessarily limiting. So I have a different approach; I have one set of CI pipelines that builds a Qt SDK for a given project, then I can use the resulting SDKs in other pipelines. Easy to update, and you can get much smaller builds too.
- vbarrielle 3y agoI've considered doing that, was it hard to set up?
- jchw 3y agoI've never tried to make a terribly general attempt at it, but I have done it a couple times and had it work pretty well. Here's one of the latest attempts I've done, although I'll note I still haven't managed to get an actual working Apple Silicon build. It keeps building for x64. The Windows builds were smooth sailing since I didn't need to worry about cross compilation yet, though I'm sure it'll be interesting when I eventually try this for AArch64 Windows. https://github.com/puyonexus/qt-sdk-builder https://github.com/puyonexus/qt-sdk-builder (I don't do this for Linux since it's easy to get a Qt SDK on Linux.)