-
Notifications
You must be signed in to change notification settings - Fork 48
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
Refresh QT Framework #14
Comments
Ack, though, while Qt's latest 5.15 release is already 5.15.5 (commercial only, though), the latest opensource one is 5.15.2 indeed. We will have to figure out how to proceed as Qt decided to not even backport security related fixed back to the public release branches. How do other linux distributions handle that currently?
Should be fairly easy by just changing |
Since Qt decided on maintaining the LTS 5.15 branch only for commercial users, Debian started to maintain its own patchset - monitoring security and stability related patches within the Qt6 repo and potentially backport them for 5.15. |
KDE is indeed also maintaining its own fork/patchset for Qt5.15, while debian does the same: https://salsa.debian.org/qt-kde-team/qt/qtbase/-/tree/master/debian/patches |
@mirko I'm not sure if I have to create another issue, but I want to note that the makefiles for Qt no longer works, it seems that the 5.15.0 package no longer exist on Qt server. I tried changing it to 5.15.2 together with the hash but it doesn't compile. In particular, the compiler says this:
So I tried deleting the
EDIT: for now I've "solved" by using this Makefile for QT 5.12: https://github.com/Lankaster/qt5-openwrt |
@JackHack96 it seams, you try to compile QT without framebuffer, but Makefile doesn't support it: |
[WIP] Upgrade to 5.15.2 and add Debian patches: https://github.com/Lankaster/video/tree/qt-5.15.2 |
@Lankaster Ok I've tried using your updated branch. First I still had to change the
EDIT: I've managed to compile I'm also trying to add qtxmlpatterns to the build as I need it. |
can qt6 be added? |
What is the status of this ticket? There is always this PR: |
The text was updated successfully, but these errors were encountered: