Skip to content
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

Fix CI Windows builds #656

Merged
merged 3 commits into from
Aug 23, 2022
Merged

Conversation

FreezyLemon
Copy link
Contributor

After FFmpeg release 5.1, gyan.dev updated their "latest" release from 5.0.1 to 5.1, which currently breaks the build (ffmpeg-next and ffmpeg-sys-next don't support 5.1 yet). To circumvent this in the future, I've fixed the version to 5.0.1 and switched to the GitHub mirror (older releases get removed from gyan.dev at some point).

This requires removing the cache functionality, because there's no way to get a file hash from GitHub release assets. This doesn't affect the build time much though.

I've tested this on my fork already, and it works without a problem.

Ignore the 2 commits, I'm just too lazy to squash them manually :D

@FreezyLemon
Copy link
Contributor Author

It seems like ffmpeg-next is about to get updated for FFmpeg 5.1 anyways. I'll update the PR when that happens

@FreezyLemon
Copy link
Contributor Author

Ok, this can be merged after #658.

@redzic redzic force-pushed the win-build-fix-ffmpeg branch from 6eb1235 to 3f296c3 Compare August 22, 2022 13:57
@mergify mergify bot merged commit a8b276c into master-of-zen:master Aug 23, 2022
@FreezyLemon FreezyLemon deleted the win-build-fix-ffmpeg branch October 22, 2022 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants