In addition to standard Cargo.toml features, this crate exposes several compile-time flags based on the FFmpeg installation detected on your system. You can use these flags in your code (e.g., using #[cfg(feature = "...")]) to handle version-specific APIs or features.
To see the full details of what the build script detects, run cargo build -vv.
### Available Feature Flags
#### FFmpeg Version Flags
Indicates the FFmpeg installation is at least version `<x>.<y>`.
Example: `ffmpeg_4_4` indicates FFmpeg version >= 4.4.
- `ffmpeg_3_0` through `ffmpeg_3_4`
- `ffmpeg_4_0` through `ffmpeg_4_4`
- `ffmpeg_5_0`, `ffmpeg_5_1`
- `ffmpeg_6_0`, `ffmpeg_6_1`
- `ffmpeg_7_0`, `ffmpeg_7_1`
- `ffmpeg_8_0`, `ffmpeg_8_1`
- `ffmpeg_9_0`
#### AVCodec Version Flags
Indicates if the `avcodec` version is greater than a specific version.
Example: `avcodec_version_greater_than_58_90`
#### API Feature Flags
Used to check for specific feature availability or deprecation guards.
- `ff_api_<feature>` (e.g., `ff_api_vaapi`): Enabled if the feature's uppercase deprecation guard evaluates to true.
- `ff_api_<feature>_is_defined` (e.g., `ff_api_vappi_is_defined`): Enabled as long as the corresponding deprecation guard is defined.