-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Mac Qt6 Builds #59177
Mac Qt6 Builds #59177
Conversation
🪟 Windows buildsDownload Windows builds of this PR for testing. 🪟 Windows Qt6 buildsDownload Windows Qt6 builds of this PR for testing. 🧮 Vcpkg update report |
Added a little quality of life improvement where this will report on library updates |
Should we drop the existing Mac workflow now? I can't see many benefits of retaining it since it's a build-only test, and this should nicely cover that. (Plus it'd release the road block preventing us upgrading the minimum python version). |
There are two things this doesn't currently cover:
A few other things in the category nice to have:
|
Unless I'm mistaken the current Mac build doesn't include these either, right?
Valid point, but I don't think a qt5 build without tests or usable artifacts is very useful.
That's all been dropped from processing, there's no need to spend effort on packaging this. If someone wants Saga functionality they can use official saga Mac install process + the community saga plugin. |
If we don't ship the product here for end users (qt5 and dmg) the python problem still persists, no?
👍 |
Could the approach used here be easily adapted to also make a qt5 build? |
Yes, we've had success with that for kadas |
If I'm not wrong the workflow is missing some build cache. |
Also many thanks @m-kuhn for making compilation of QGIS so straightforward on macOS!!! |
I think we'll need to disable/tune other workflows before we can afford more build cache otherwise we'll overuse the cache. That was one of the reasons to mark it as "draft" |
let's merge it! |
The backport to
stderr
stdout
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release-3_40 release-3_40
# Navigate to the new working tree
cd .worktrees/backport-release-3_40
# Create a new branch
git switch --create backport-59177-to-release-3_40
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 51a21bd99a24da8dff16504ee02ccfef7cac7e9d,529ac6f7ce88f12337d1e272baa3a9084e3d32fe,ed08e3983b45a8a872bdbcce51d4866903e665de,443d09cda3a2e5746d0b00bee0008321e9acbf93,d9e68a1b852815261cc7a12ef0dfb1c34bae89d7,765e02bd68e14aaca04016acd832053029f2252b,9dd08475333ee3d7fa8b7c23f248c956a36c8c4c,9339143a0af92e4a7f08c9dd6149d5ed12d637c7,2f7dc21d842e5db548855158b7e98df281b12e3c,e7b9f5ca2bad4d0c653f1fd4ab0be66187cfa7f6,d1e63f61aab92283b779eaeb4ac982d9f4a81784,d1e0bb6f817acbdeae3c490c7f63d3de16b9a05a,d277e8420fae5fbd616a2e37162e9786011917e9,bc745957bf316f29e5c063146bc66444c6064838
# Push it to GitHub
git push --set-upstream origin backport-59177-to-release-3_40
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release-3_40 Then, create a pull request where the |
Work in progress
Build instructions