The MinGW path kept fighting the environment (the GitHub image's MSVC INCLUDE/LIB poison the GNU compiles; ocio-sys' fork then dragged the MSVC-only headers into g++ and died on vcruntime.h). The Windows jobs on both workflows now: - run on warp-windows-2025-vs2026-x64-16x (preinstalled VS 2026) with the stable MSVC Rust toolchain; - install dependencies through vcpkg MANIFEST mode: vcpkg.json at the repo root carries FFmpeg with every free codec + hwaccel (mirroring build-ffmpeg.sh's configure), pkgconf and librsvg; the vcpkg_installed tree plus the binary-cache archives are cached on the manifest hash with save-always; - build OCIO bundled (ocio-sys' vendored sources are what MSVC wants — the MSYS2 package was the workaround, not the preference), so OCIO_RS_NO_MSVC_INCLUDES is gone; - ship the vcpkg runtime DLLs next to the binaries in the NSIS installer with a static-CRT release build (no vcruntime DLLs), replacing the ntldd-based MSYS2 bundling. FFmpeg version pinning via builtin-baseline is a documented follow-up: the Configure step logs vcpkg list so the first green run reports the resolved versions. docs/build.md keeps the MSYS2 flow as the local alternative and points at the CI path.
10 lines
380 B
YAML
10 lines
380 B
YAML
# actionlint configuration: whitelist the WarpBuild runner labels used by
|
|
# the CI/CD workflows so `actionlint ci.yml` / `actionlint cd.yml` passes.
|
|
# See https://github.com/rhysd/actionlint/blob/main/docs/config.md
|
|
self-hosted-runner:
|
|
labels:
|
|
- warp-ubuntu-latest-x64-8x
|
|
- warp-windows-latest-x64-16x
|
|
- warp-windows-2025-vs2026-x64-16x
|
|
- warp-macos-26-arm64-6x
|