-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fixed #12042 - deprecated building with Qt5 / build with Qt6 in CI / updated latest Qt in CI to 6.5.3 #4957
Conversation
I removed the CI files so this does not trigger a build to ease things. So please review the individual commits as the CI changes are not visible. |
qmake
build system / removed fallback when using USE_QT6=On
/ build with Qt6 in CIqmake
build system and Qt5 / removed fallback when using USE_QT6=On
/ build with Qt6 in CI
Using Qt6 seems to switch the whole project to C++17 leading to unexpected clang-tidy warnings and the runtime of the clang-tidy step seems to be balloon because of it. Also there seems to be no Qt6 on ubuntu 20.04 so deprecating Qt5 should be fine but dropping it (even though EOL) doesn't seem like an option in the near future. |
qmake
build system and Qt5 / removed fallback when using USE_QT6=On
/ build with Qt6 in CI17c1e25
to
e0c7846
Compare
fdc5285
to
4434ad3
Compare
… also avoids `-Wctad-maybe-unsupported` Clang compiler warnings with Qt6
Qt 5.15 will be EOL on May 26 so we should start switching away from it. We already have issues with many of the previous versions and qmake on legacy distros so we should cut that off.
I will add a Qt6 release build for Windows in another PR so it can be tested. We should switch to it as the delivered build after the next release and stop using Qt5 altogether in the CI in the release afterwards (that would get rid of several build steps). We could leave it so you could still try to build it but no longer support it so it is up to the user to get it to work before removing it completely later on.