Mostly for the record, since I have a class I ought to be working on for my day-job this month.
So, for obvious reasons, after the switch to qt6 I can no longer build Seamly with qt5. The repository I use doesn’t have qt6 yet, & I’m having trouble figuring out the qt website. So I decided to see about using the AppImages until I could get that wrangled. The AppImage wouldn’t run, the pre-qt6 AppImage wouldn’t run. I tried opening it from the Terminal & got this error:
/tmp/.mount_SeamlyKIehbK/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/.mount_SeamlyKIehbK/usr/bin/../lib/libFLAC.so.8)
/tmp/.mount_SeamlyKIehbK/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /tmp/.mount_SeamlyKIehbK/usr/bin/../lib/liblzma.so.5)
/tmp/.mount_SeamlyKIehbK/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /tmp/.mount_SeamlyKIehbK/usr/bin/../lib/liblzma.so.5)
As well as a lot of similar ones. In short I do not have any LIBC above GLIBC_2.31, so it won’t run. Which seems a bit odd, since I was able to build, install, & run up through the 07.28 edition (I haven’t bothered with the 08.04, & the newer ones are qt6.)
So, I guess I’m wondering why the AppImage requires a newer build environment to run than is required to build Seamly?
Anyway, I guess I’ll get back to trying to figure out how to install qt6, so I can build Seamly again.
Either that, or do all my testing latest releases on my Chromebook, which for some reason still runs AppImages fine.
PM me if you need help guiding you through installing Qt6 and setting it up. There’s a alot of stuff you don’t need to install from the Qt maintainer. However if you want to build with the MSVC kit you also need to install Visual Studio to get the Qt tools. Since using Qt6 I haven’t built with GCC, but I don’t see it as an issue. When using the MSVC kit there’s also a bunch of environmenal variables that need to be set… which I had to search all over the place to find what to add as it was rather obscure info. I added a disccusion awhile back that outlines the addiitons that need to be made. It’s for Qt 6.2.4, and we’re now using 6.5.3 so you just need to replace references to 6.2.4 with 6.5.3.
I’m glad I did that wayback when as I’ve had to refer back to it when we actually migrated to Qt6.5.3.
It’s actually been a while since any of my desktops would run the AppImage. I was probably using Ubuntu 20, but it hadn’t notified me of an upgrade, & since I was able to at least build it in Devuan, which fit the way I was using it better anyway, I just switched over.
I see, Devuan 4 was released in 2021, so the libc version is also from at least that or older (as its Debian-based). Current would be Devuan 6, released this year, and I am confident that the AppImage from Seamly runs on Devuan 6.
Now that our lawsuit from the shop fire has been settled I’m going to be getting a MacBook so I can finally build and run the Mac version. Anything I should know about installing Qt for the Mac and building the apps? Like will Seamly build and run for the latest M-Series and current OS?
Great to hear, and already thank you for picking this up!
Seamly will run on the latest M-Series, and will build as well. We are using m-series based github runners already, and I try it occasionally on my wifes M1 macbook.
Installing works just as on Windows, the default Qt downloader will do. Installing Xcode from the AppStore will give you a working C++ compiler, then its just Qt 6.5 via downloader
Good to hear. Also I brought up at this week’s meeting about maybe bumping up the Qt6 version… now that the builds seem relatively stable, and seems to build on 6.10. What’s your opinion?
Ok. I’ll clear out my Qt5 so I have room to install 6.10… and see how that builds. If there are no issues building, and we can have a runner on Github build with 6.10 - I just assume we bump up to that. We should then be set for awhile.
Also at some point I’d like to refactor to get rid of the deprecated Qt5 code so we don’t need the Qt5 compatibilty module.
