0d94089855
Since re-enumerating all the formats supported by FFmpeg in our bindings would be a rather large effort, it looks like a good compromise here is to allow the user to create an AvPixelFormat from the raw enum values exposed by bindgen. Add a helper that checks that the value is in range of valid formats and convert it into our enum wrapper. BUG=b:239897269 TEST=cargo test --features ffmpeg -p ffmpeg Change-Id: I3c1433e9d76d645b7615bde81433e1df2cfa3910 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3911108 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> |
||
|---|---|---|
| .. | ||
| src | ||
| bindgen.sh | ||
| build.rs | ||
| Cargo.toml | ||
| README.md | ||
| VERSIONS | ||
FFmpeg wrapper
This is a minimal FFmpeg 5.0 wrapper for use with the virtio-video device, allowing to run a virtual video device backed by software decoding or encoding. This is useful for development and testing in situations where no supported video acceleration is available on the host.
Although several FFmpeg binding crates exist, most of them are not able to link against the system FFmpeg, and the only one that does is released under a software license that makes our lawyers nervous. Also they all run bindgen at build time, which is not possible to do under the Chrome OS build system and would require to patch the crate with fully generated bindings.
So taking this in consideration, as well as the extra work that it is to depend on external Rust crates in Chrome OS, it is preferable to add our own simple bindings here that cover just the parts of FFmpeg that we need.
This crate has minimal dependencies ; on the FFmpeg side, it just uses libavcodec, libavutil and
libswscale.
The bindings can be updated using the bindgen.sh script. A few elements that bindgen cannot
generate because they are behind C macros are re-defined in avutil.rs and error.rs, as well as
tests to ensure their correctness.
And that's about it.