bindgen's output is a committed source file, so the version producing it
has to be pinned like any other input. With `bindgen = "0.72"` floating,
a patch release that changes formatting silently changes the generated
bindings.
`--locked` on the alias keeps cargo from quietly updating it when the
manifest disagrees.
Generating the FFI bindings at consumer build time is unecessary. The
`use-bindgen` Cargo feature was non-additive, and forced bindgen +
libclang onto every build that opted in, for a decision that is really
about the maintainer's environment, not the public API.
Move binding generation out of the build entirely, following the xtask
pattern[^1]:
- build.rs is reduced to locating and linking libvlc.
- Regeneration lives in a `xtask` crate, run with `cargo xtask bindgen`.
[^1]: <https://github.com/matklad/cargo-xtask>
Alaric Senat