repository·master·Indexed 21 days ago
https://github.com/larksuite/rsmpegA safe Rust wrapper around FFmpeg's inner APIs designed for robust multimedia processing. rsmpeg provides a thin layer over FFmpeg's Rust bindings, supporting FFmpeg versions 6.*, 7.*, and 8.*. It includes comprehensive guides for linking against system-wide FFmpeg installations, managing dependencies via vcpkg, and building FFmpeg from source using provided utility scripts.
rsmpeg is a thin and safe Rust layer built on top of FFmpeg's Rust bindings. Its primary purpose is to safely expose FFmpeg's inner APIs within Rust, allowing developers to build robust multimedia projects using Rust's safety guarantees instead of interacting directly with the FFmpeg C API.vcpkg. Follow the specific vcpkg tutorial for step-by-step instructions.To use rsmpeg with FFmpeg managed by vcpkg, follow these configuration steps in your Cargo.toml:
rsmpeg with the link_vcpkg_ffmpeg feature: Choose the feature flag that matches your target FFmpeg version (ffmpeg6, ffmpeg7, or ffmpeg8). You must set default-features = false.[package.metadata.vcpkg]: Define the vcpkg git repository, the specific dependencies (including the triplet), and the branch (e.g., master).cargo vcpkg build to compile the FFmpeg dependencies.[dependencies]
# Choose one based on your FFmpeg version requirement
rsmpeg = { version = "0.18", default-features = false, features = ["ffmpeg7", "link_vcpkg_ffmpeg"] }
[package.metadata.vcpkg]
git = "https://github.com/microsoft/vcpkg"
dependencies = ["ffmpeg:x64-windows-static-md"]
branch = "master"# Use --verbose to help identify errors if the build fails
cargo vcpkg --verbose buildTo manage FFmpeg dependencies via vcpkg within your Rust project, you must first install the cargo-vcpkg tool.
cargo install cargo-vcpkgconfigure script options. Refer to the source build tutorial for details.To allow cargo to find your FFmpeg installation during compilation, you must set the FFMPEG_PKG_CONFIG_PATH environment variable to the absolute path of your FFmpeg pkgconfig directory.
If you used the utils scripts, the directory is typically located at {PWD}/tmp/ffmpeg_build/lib/pkgconfig.
# macOS & Linux
export FFMPEG_PKG_CONFIG_PATH=${PWD}/tmp/ffmpeg_build/lib/pkgconfig
# Windows (CMD)
set FFMPEG_PKG_CONFIG_PATH="%CD%\tmp\ffmpeg_build\lib\pkgconfig"
# Windows (PowerShell)
$env:FFMPEG_PKG_CONFIG_PATH="$(($PWD).path)\tmp\ffmpeg_build\lib\pkgconfig"To avoid compiling FFmpeg from source, you can link rsmpeg against a system-wide FFmpeg installation. You must install the FFmpeg libraries, development headers, and pkg-config.
Debian/Ubuntu:
sudo apt update
sudo apt install libavcodec-dev libavdevice-dev libavfilter-dev libavformat-dev libavutil-dev libpostproc-dev libswresample-dev libswscale-dev pkg-configmacOS (Homebrew):
brew install ffmpeg pkg-configVerify that pkg-config can locate your installation by running:
pkg-config --modversion libavcodecpkg-config --modversion libavcodecwinget. This is the easiest way to use BtbN's feature-rich builds. Refer to the winget tutorial for the specific command and setup steps.If your build target is Windows, you must create a .cargo/config.toml file in your project workspace to link the necessary system libraries required by FFmpeg.
[target.x86_64-pc-windows-msvc]
rustflags = [
"-C", "link-arg=Mfplat.lib",
"-C", "link-arg=Strmiids.lib",
"-C", "link-arg=Mfuuid.lib",
"-C", "link-arg=Bcrypt.lib",
"-C", "link-arg=Secur32.lib",
"-C", "link-arg=Ole32.lib",
"-C", "link-arg=User32.lib"
]vcpkg package manager to facilitate integration with rsmpeg.rsmpeg.Add rsmpeg to your Cargo.toml. You must select a feature flag that matches the version of FFmpeg you have compiled.
features = ["ffmpeg6"] and disable default features.features = ["ffmpeg7"] and disable default features.# FFmpeg 6.*
rsmpeg = { version = "0.18", default-features = false, features = ["ffmpeg6"] }
# FFmpeg 7.*
rsmpeg = { version = "0.18", default-features = false, features = ["ffmpeg7"] }
# FFmpeg 8.* (feature `ffmpeg8` is enabled by default)
rsmpeg = "0.18"