4 Commits

Include renames

Author	SHA1	Message	Date
Mike-Solar	faebc79c31	ci/cd: Windows goes vcpkg manifest + MSVC on the VS 2026 runner ... 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.	2026-09-11 15:59:39 +08:00
Mike-Solar	f9b1863e5f	ci: move CI back to GitHub Actions, add a macOS job ... The Gitea migration left CI on the self-hosted instance with every cache commented out and the CD workflow broken at parse time (kiname:). CI runs on GitHub-hosted runners again: - Linux: ubuntu-latest with the rust toolchain from dtolnay/rust-toolchain (the self-hosted runner's custom RUSTUP_HOME/CARGO_HOME lines are gone) and the cargo + FFmpeg caches re-enabled. - Windows: windows-latest with msys2/setup-msys2 provisioning the UCRT64 environment (the Gitea runner had it preinstalled); the msys2 {0} shell, the GNU-target MSYS2 Rust, the OCIO_RS_NO_MSVC_INCLUDES gate and the -lmsvcrt link-order workaround carry over, as do both caches. - macOS: new job on macos-14 (Apple Silicon) — Homebrew deps, vendored static OCIO, cached FFmpeg, cargo check + the full suite with the same retry-once flake policy. CD fixes: the kiname: typo that kept the workflow from parsing, the Warp runner labels become the standard GitHub ones, and all eight commented-out cache blocks are restored. The gpui submodule URL follows the move to GitHub, the README badge points at the GitHub workflow, and the .gitea directory is dropped.	2026-09-11 08:57:05 +08:00
Mike-Solar	1564844bab	gitea: move workflows to .gitea, disable caches; settle the keystroke flake ... Gitea prep: .github becomes .gitea (the act runner looks there), and every actions/cache + Swatinem/rust-cache step is commented out until the self-hosted instance has a cache provisioned. The remaining marketplace actions (checkout/upload-artifact are act-compatible; msys2/setup-msys2, dtolnay/rust-toolchain and softprops/action-gh-release need a runner test / replacement) are a follow-up. tests: the two gpui keystroke tests that flaked on Windows CI (undo pair, snapping toggle — each once, values identical to the pass state, Global-route keys) now dispatch each key with a double park. The root cause is not fully pinned: the loss happens inside gpui's synthetic key dispatch on Windows (both tests hold every test lock; production is unaffected). The CI retry-once remains the backstop. The earlier idea of advancing the simulated clock to flush gpui's pending-input timer is off the table: the mock engine's playback ticks with executor time, so a clock advance moves the playhead out from under the assertions (observed: playhead 14 vs expected 9).	2026-08-21 23:53:14 +08:00
Mike-Solar	8334894984	ci(cd): packaging verified end-to-end on macOS ... - every job builds -p oakengine first (the dylib is a build-dep-only artifact otherwise and cli/worker link-search the profile dir) - 512px icon (tauri-icns only maps 512@1x/1024@2x); dylib embedding derives the path from the binary's otool reference; fpm invoked from the gem bin dir; GITHUB_ENV blocks batched (SC2129); actionlint.yaml whitelists the warp runner labels - Windows job disabled with a reference block until the engine links there - real run: Oak-macOS-arm64.dmg produced, app launches from the volume (known gap recorded: the dmg still dynamically links Homebrew codec libs; not self-contained yet)	2026-08-16 18:05:03 +08:00