Cross platform FFI bindings for FFmpeg inner libraries. This is a crate that:
- Linking FFmpeg libraries for you.
- Generates Rust binding for FFmpeg libraries.
To use this crate, you need to set several environment variables.
The simplest usage:
Build ffmpeg statically and set
FFMPEG_PKG_CONFIG_PATH to the path of the generated FFmpeg
pkg-config files. And you don't need to set other environment variables for static linking.
FFMPEG_PKG_CONFIG_PATH to some placeholder value will let
rusty_ffmpeg probing system library.)
rusty_ffmpeg can link FFmpeg using
vcpkg, check documentation of the vcpkg crate for the environment variables to set, then it works.
You need to set several environment variables for both linking and binding generating procedure.
Dynamic linking with pre-built dylib: Set
FFMPEG_DLL_PATHto the path of
so. (Windows: Put corresponding
.libfile next to the
Static linking with pre-built staticlib: Set
FFMPEG_LIB_DIRto the path of the FFmpeg pre-built libs directory.
To generate bindings:
Compile-time binding generation(requires the
FFMPEG_INCLUDE_DIRto the path to the header files for binding generation.
Use your pre-built binding: Set
FFMPEG_BINDING_PATHto the pre-built binding file. The pre-built binding is usually copied from the
OUT_DIRof the compile-time binding generation, by using it you don't need to regenerate the same binding file again and again.
FFI is not that easy, especially when you are dealing with a big old C project. Don't feel depressed when there are some problems. The CI check already have some typical ffmpeg compilation and use cases for you to check. File an issue if you still have any problem.