-
Notifications
You must be signed in to change notification settings - Fork 12
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
Doesn't build: ffmpeg-next non-exhaustive patterns #92
Comments
What is your ffmpeg version |
This seems to be a bug in ffmpeg-next, this should workaround it diff --git a/Cargo.toml b/Cargo.toml
index 86bdc01..f7f7bb5 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -27,7 +27,7 @@ wayland-protocols = { version = "0.32", features = [
"staging",
] }
wayland-protocols-wlr = { version = "0.3", features = ["client"] }
-ffmpeg-next = "7.0.1"
+ffmpeg-next = { version = "7.0.1", features=["rpi"] }
ffmpeg-sys-next = "7.0.0" # need direct dep on -sys to get metadata to consume in build.rs
thiserror = "1.0.38"
human-size = "0.4.2" |
Thanks, it seems to have worked |
I think I have a similar issue with ffmpeg-next:
Huge caveat that I do not understand how Cargo.toml handles versions. The toml says "7.0.1" but the compile log references to "7.1.0"? Very confusing. |
That's strange--this seems like a bug in ffmpeg-sys. What distro are you on? Re cargo versions: version constraings are "semver minimums" in that any semver compat version is OK. So, cargo is allowed to select 7.1 when I specify 7.0 but it's not allowed to select 8.0. https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html if you're curious |
I am using my own rolled distro (based on LFS). The compilation issue on v0.1.6 went away when I upgraded to FFmpeg 7.1.0 (the C library). |
System: Gentoo, ffmpeg version is 6.1.2
The text was updated successfully, but these errors were encountered: