Some checks failed
CI / Windows build (push) Has been cancelled
Make the Gitea CI maximally likely to produce a usable Windows .exe on a self-hosted runner behind the GFW, since compilation must go through CI: - Build is the priority: format/analyze/test now run with continue-on-error so a toolchain-version lint difference can never block the actual compile. - ONNX Runtime download: default HTTP(S)_PROXY to the local proxy (http://127.0.0.1:7890, overridable via repo secrets) so CMake's file(DOWNLOAD) can fetch it; documented system-install alternative. - Checkout stays on the gitea.com mirror, with a commented manual-checkout fallback (clones from the local Gitea) if gitea.com is unreachable. - Artifact upload is best-effort; an explicit step prints the Release output path so the binary is findable even if upload fails. - Dropped the optional server job to keep the Windows build focused. - README: documented the runner prerequisites (Flutter on PATH, VS C++ build tools, proxy, gitea.com, host-mode runner) that the workflow can't set. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
3.8 KiB
3.8 KiB