moq-vaapi 0.0.2

(AI GENERATED) VA-API H.264 hardware encoder, derived from discord/cros-libva + discord/cros-codecs
# moq-vaapi

> **⚠️ AI GENERATED.** This crate was written by an AI agent (Claude), using the
> repositories below as references. How closely individual files track upstream
> varies and the emitted bitstream has not been validated at playback — treat the
> whole thing as derived, unverified work and review before relying on it.

A small, self-contained **VA-API H.264 hardware encoder** for Linux (Intel / AMD),
derived from
[discord/cros-libva @ discord-0.0.13](https://github.com/discord/cros-libva/tree/discord-0.0.13)
and
[discord/cros-codecs @ discord-0.0.5](https://github.com/discord/cros-codecs/tree/discord-0.0.5)
— both BSD-3-Clause, themselves forks of Intel's
[cros-libva](https://github.com/intel/cros-libva) (ChromiumOS).

It exists to give [moq](https://github.com/moq-dev/moq)'s `moq-video` a thin,
crates.io-publishable VA-API encoder brick instead of a multi-backend framework
pulled in as a git dependency.

## What it does

- **H.264 encode** over VA-API: tightly-packed NV12 in, an Annex-B elementary
  stream out (packed SPS/PPS + slice headers, low-latency IPPP, rate control).
- **Pinned, vendored headers.** libva's headers are vendored into
  [`libva/`]./libva (see `just vendor`) and fed to bindgen, so generating the
  bindings needs **no system libva-dev** — only `libclang` — and the pinned
  version means a system libva bump can't drift the bindings.
- **Links system libva on Linux.** The generated `va*` symbols are resolved by
  linking the system `libva` / `libva-drm` (via pkg-config), so a `vaapi`-enabled
  binary requires `libva.so` present at runtime — fine for a build that targets
  VA-API hardware. VA-API's ABI is stable, so a newer system libva links against
  the pinned bindings. (On non-Linux hosts the crate only builds as an rlib, which
  leaves the symbols for the final binary, so it stays compilable for development.)

## Layout

- `src/` — libva bindings (`bindings`, `display`, `surface`, `buffer`, ...), the
  H.264 bitstream layer (`bitstream_utils`, `codec::h264`), and the thin encode
  driver (`encode`).
- `libva/` — vendored libva headers (checked in; refreshed by `just vendor`).
- `build.rs` + `bindgen_gen.rs` + `libva-wrapper.h` — bindgen setup.

## Development

Recipes run inside the nix devShell:

```sh
nix develop --command just check     # clippy + fmt
nix develop --command just ci        # check + cargo-deny
nix develop --command just vendor    # refresh libva/ headers from upstream
```

The crate compiles on any OS (macOS included) — the rlib build is header-only and
defers the libva link to the final binary, which is Linux-only.

## Licensing

BSD-3-Clause (see [`LICENSE`](./LICENSE)). Vendored upstreams keep their notices:
[`LICENSE.cros-codecs`](./LICENSE.cros-codecs) and the vendored libva headers
under [`LICENSE.libva`](./LICENSE.libva) (MIT).