Text chat 63 follow-up: FFmpeg bindings for the Windows runner, MSVC link check #442

Closed
opened 2026-11-13 08:07:14 +00:00 by charles · 1 comment
Owner

Follow-up of Text chat 63 (#403), for Task 64 (#404), which is the first crate to link FFmpeg.

  1. Pre-generated bindings. The plan wants the Linux job to generate rusty_ffmpeg's binding.rs once per FFmpeg version and the Windows job to reuse it (FFMPEG_BINDING_PATH), so the Windows runner needs no libclang. Revision 1 of the FFmpeg archives (ffmpeg-8.0.3-r1) carries no binding.rs: generating it needs bindgen with the Windows target's layout (long is 32-bit there), which build.sh cannot do without a Rust toolchain. cargo xtask ffmpeg env already exports FFMPEG_BINDING_PATH whenever an archive has binding.rs at its root. Either add it to build.sh (bindgen-cli against the mingw headers with --target=x86_64-pc-windows-gnu, bump revision), or install a pinned LLVM on the Windows runner and set LIBCLANG_PATH in ci.yaml/release.yaml.
  2. MSVC link of the MinGW DLLs. The Windows archive's import libraries (lib/avcodec.lib, ... from llvm-dlltool) are checked to export the symbols (llvm-nm) but no MSVC-built program has linked them yet (no Windows machine in that task). Task 64's Windows run is the first; if it fails, the plan's fallback is BtbN's pinned win64-lgpl-shared build of the same line.
Follow-up of Text chat 63 (#403), for Task 64 (#404), which is the first crate to link FFmpeg. 1. **Pre-generated bindings.** The plan wants the Linux job to generate rusty_ffmpeg's `binding.rs` once per FFmpeg version and the Windows job to reuse it (`FFMPEG_BINDING_PATH`), so the Windows runner needs no libclang. Revision 1 of the FFmpeg archives (`ffmpeg-8.0.3-r1`) carries no `binding.rs`: generating it needs bindgen with the Windows target's layout (`long` is 32-bit there), which build.sh cannot do without a Rust toolchain. `cargo xtask ffmpeg env` already exports `FFMPEG_BINDING_PATH` whenever an archive has `binding.rs` at its root. Either add it to build.sh (bindgen-cli against the mingw headers with `--target=x86_64-pc-windows-gnu`, bump `revision`), or install a pinned LLVM on the Windows runner and set `LIBCLANG_PATH` in ci.yaml/release.yaml. 2. **MSVC link of the MinGW DLLs.** The Windows archive's import libraries (`lib/avcodec.lib`, ... from llvm-dlltool) are checked to export the symbols (`llvm-nm`) but no MSVC-built program has linked them yet (no Windows machine in that task). Task 64's Windows run is the first; if it fails, the plan's fallback is BtbN's pinned `win64-lgpl-shared` build of the same line.
charles added this to the Text chat milestone 2026-11-13 08:07:14 +00:00
Author
Owner

Done on textchat (c24495a): committed bindings tools/ffmpeg/bindings/8.0.3-r1-win-x64.rs (xtask/src/ffmpeg.rs:36-38); the Windows release (Setup.exe) links FFmpeg

Closed during the 2026-11-14 issue triage.

🤖 Generated with Claude Code

Done on `textchat` (c24495a): committed bindings `tools/ffmpeg/bindings/8.0.3-r1-win-x64.rs` (`xtask/src/ffmpeg.rs:36-38`); the Windows release (Setup.exe) links FFmpeg Closed during the 2026-11-14 issue triage. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#442
No description provided.