-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qt4 dropped on Ubuntu 20.04, Qfsm needs port to qt5 #1
Comments
As a short term solution I have added an AppImage package to the latest release that works across all modern Linux distributions. This doesn't change the fact however that Qfsm needs to be ported to newer requirements in future - qt4 will die out sooner or later. |
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
As an FYI, the AppImage fails to run on current Arch with:
I'm not quite sure what's going wrong here. I had a look at the extracted squashfs and
All the Qt libs appear to be coming from the AppImage squashfs, so not sure how it ends up loading the system Qt libraries. Dynamic loading maybe? Might want to include all of Qt in the AppImage in case that's what it is. NB: It's a perfectly valid strategy to use AppImage instead of porting to Qt5/6. There's no reason to spend time on porting instead of feature development or bugfixing, ie the core functionality. |
OK, tracked it down:
So it's reading my systemwide Qt styling, using the adwaita theme plugin pursuant to that, and horribly failing since my system has a slightly newer Qt4. Theme plugins tend to use private Qt headers so are ABI incompatible across minor version bumps. I have not figured out how to launch it with whatever the default is. Unsetting I'm not sure what the 'correct' fix is for this. Options would be:
For me, I just built qfsm from source since I use a non-broken distro and have Qt4. As an FYI, you have CMake artifacts from an in-progress build checked into the repo in PS: Qfsm looks very nice, thank you for writing it. Playing around with Verilog will be fun. The Ragel export might also come in handy. Assuming it all works as advertised, of course ;) |
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
there seems to be an active fork. see AaronErhardt/qfsm#1 for their progress on qt5 support
qt4 is no longer available for Ubuntu 20.04, which means that Qfsm no longer works with the latest Ubuntu releases. graphviz is not affected by this change.
There seems to be no reasonable workaround for this problem so far, so the best solution would be to port Qfsm to qt5 (which has been around since 2012!!) or even directly to qt6 which will be released in a few months.
Anyway, I don't have time to solve this right now (nor do I have a lot of experience with qt), so any help would be much appreciated :)
The text was updated successfully, but these errors were encountered: