Upgrade to libdjinterop 0.21.0#13233
Conversation
|
The build errors confuse me. From the macOS build: These two functions changed their signature from accepting Is there something cached in these builds that would somehow pick up the old signature? |
Yes, the vcpkg build environment has probably the headers of the old version. We need to update this anyway, because the windows build fails with the downloaded source for some reasons. |
Ok, I'm not sure how to resolve this - @daschuer are you ok to make (or show me how to make) the necessary changes to get this through? |
|
It is best to create a vcpkg upstream PR and then cherry-pick it from our https://github.com/mixxxdj/vcpkg branches. |
|
PR to for libdjinterop 0.21.0 in vcpkg: microsoft/vcpkg#38888 |
|
Great, thank you. Now we need to cherry pick it to our own vcpkg repro. To the 2.4 and 2.5 branch. |
|
Here we go - hopefully I've done this right:
|
|
I think you will have to rebase your branch against |
|
The 2.4 target is correct, because 2.4 and main builds are broken. |
|
@daschuer Now that the vcpkg PRs are merged, please can you re-run the failed actions? I don't appear to have permission to do this. Thanks! |
|
I doubt that the rerun will be enough, because we need to adjust the buildenv hashes before. |
@JoergAtGithub I'm not familiar with what this means, but the Windows build is already failing with a similar error to before, so I suspect you're right. What steps need to be taken now? |
|
You need to do similar changes as in #12067 , otherwise the Mixxx build will not download the new buildenv zip files. |
|
Thank you for your help. |
No description provided.