ramp-ffmpeg-sys 9.0.2

RAMP Stack FFmpeg bindings with bundled source and Apple static linking
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

[![ramp-ffmpeg-sys on crates.io](https://img.shields.io/crates/v/ramp-ffmpeg-sys)](https://crates.io/crates/ramp-ffmpeg-sys)

RAMP Stack's fork of [ffmpeg-sys-next](https://github.com/zmwangx/rust-ffmpeg-sys),
originally derived from [ffmpeg-sys](https://github.com/meh/rust-ffmpeg-sys).
It includes the Apple framework-linking fix, bundled FFmpeg 9.0.2 C source, and
pregenerated Apple bindings. The safe wrapper is
[ramp-ffmpeg](https://github.com/ramp-stack/ffmpeg).

## Building

The default features compile the bundled C source into static libraries with portable
CPU settings. macOS and iOS builds use pregenerated bindings, so no installed FFmpeg,
pkg-config, libclang, Git, or build-time source download is required. A native C
compiler, Make, and the target SDK are still required; Intel builds also require NASM.
On Apple platforms, install Xcode's command-line tools and the SDK for the target.

The pregenerated bindings cover Apple Silicon and Intel macOS, arm64 iOS devices,
and arm64/x86_64 iOS simulators. They are used only with the bundled FFmpeg source.
Other targets and system/prebuilt FFmpeg installations require the explicit
`generate-bindings` feature and libclang. To use an installed FFmpeg, disable default
features and enable `generate-bindings` plus the required component features.

The bundled source and its provenance are described in [vendor/README.md](vendor/README.md).
FFmpeg retains its own licensing; see [LICENSE.md](LICENSE.md).

A word on versioning: major and minor versions track major and minor versions of FFmpeg, e.g. 4.2.x of this crate has been updated to support the 4.2.x series of FFmpeg. Patch level is reserved for bug fixes of this crate and does not track FFmpeg patch versions.

## Feature flags

In addition to feature flags declared in `Cargo.toml`, this crate performs various compile-time version and feature detections and exposes the results in additional flags. These flags are briefly documented below; run `cargo build -vv` to view more details.

- `ffmpeg_<x>_<y>` flags (new in v4.3.2), e.g. `ffmpeg_4_4`, indicating the FFmpeg installation being compiled against is at least version `<x>.<y>`. Currently available:

  - `ffmpeg_3_0`
  - `ffmpeg_3_1`
  - `ffmpeg_3_2`
  - `ffmpeg_3_3`
  - `ffmpeg_3_4`
  - `ffmpeg_4_0`
  - `ffmpeg_4_1`
  - `ffmpeg_4_2`
  - `ffmpeg_4_3`
  - `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_greater_than_<x>_<y>` (new in v4.3.2), e.g., `avcodec_version_greater_than_58_90`. The name should be self-explanatory.

- `ff_api_<feature>`, e.g. `ff_api_vaapi`, corresponding to whether their respective uppercase deprecation guards evaluate to true.

- `ff_api_<feature>_is_defined`, e.g. `ff_api_vappi_is_defined`, similar to above except these are enabled as long as the corresponding deprecation guards are defined.