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
Update minimum platforms for 1.15.0 to update Qt #3461
Comments
The other dependency updates we can deal with, but let's focus on Qt6. The first step to get that in is to get rid of Qt4 conditionals. |
I've been studying the Qt (LTS only, because non-LTS only has 1 year support) requirements a bit from the site @alamshafil mentioned above.
So basically we can get:
I don't think 5.15 is worth it for -10 months of support. After doing mad patching on pinned Qt source code, I'm convinced that 6.5 is the best option, because that means we don't have to worry about mad patching for 2 years. However, we'd need to check if we can get this to work for linux with glibc 2.31 as a base (current version for focal/bookworm - under RH 9.2, which iirc has 2.34) I could - on top of #3466 and #3465 - investigate what is needed to just allow qt6 as a self-compile dependency for now. This would mean that we'd first make it work separate from |
I wanted to open this issue to discuss if should update minimum platform versions (Windows, macOS, Linux), which is a breaking change, to help update the Qt dependency.
According the the Qt website, Qt 5.15.x supports macOS >= 10.13 and Windows >= 7.
Qt 6.6 supports macOS >= 11 and Windows 10 (1809) or higher.
Updating the Qt dependency also requires new dependencies.
Dependencies update:
New Dependencies
The Qt dependency update would cause the change in minimum platform support. While OpenSSL should support glibc 2.11, from the last time I attempted to update the Qt version I noticed symbol check failed on
getauxval
andgetentropy
.It also might be helpful to do these dependencies updates, but I am not sure how it will effect the current Qt version.
The text was updated successfully, but these errors were encountered: