-
Notifications
You must be signed in to change notification settings - Fork 238
Build logic: Add Qt6 compatibility #2328
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
Conversation
|
I initially targeted all the Qt6 stuff for 3.9.0, but looking over the diff it might be safe to merge before 3.8.2rc1? What do others think? |
|
I've no particular objection - albeit we've entered the beta cycle, so it's cutting down the test period for the new style of building. |
softins
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks good to me. I haven't run it, but the CI looks happy.
I initially targeted all the Qt6 stuff for 3.9.0, but looking over the diff it might be safe to merge before 3.8.2rc1? What do others think?
As this is just improving the build process, I would be happy to merge it. I wouldn't want to add the code changes before 3.8.2, but I don't think you were suggesting that.
This updates the Github Autobuild workflow to make the Xcode version configurable through the build matrix. This helps when different macOS targets should be built by different Xcode versions.
Co-authored-by: Christian Hoffmann <mail@hoffmann-christian.info>
With Qt 6.2 the binary location path changed from `clang_64` to `macos`. Therefore, check both places now to support the full range of relevant Qt releases.
4af1bd3 to
f454dab
Compare
|
Alright. I've just added a commit to add a Changelog entry and will merge today when CI is green again. |
Short description of changes
This PR makes the (auto)build handling ready for Qt6. In detail:
Context: Fixes an issue?
Qt6 support, see #2299 for details.
Does this change need documentation? What needs to be documented and how?
No.
Status of this Pull Request
Ready, I'm not planning further changes right now.
What is missing until this pull request can be merged?
Checklist
My code follows the style guide