memlnaut-nisps/.github/workflows
monkey-w1n5t0n aa60fbb466 fix(build): resolve a bare EMCC command name in build-wasm.sh
Third failure uncovered by the restored pipeline. With checkout and the C++
build fixed, CI reached the WASM step and died on `[build-wasm] emcc not found
at emcc`: ci.yml passed `EMCC: emcc`, but the script's existence check
(`[[ ! -x "$EMCC" && ! -f "$EMCC" ]]`) only understands paths, so it looked for
a file literally named "emcc" in the working directory. This has been broken
for as long as the override existed; it was invisible because CI never got past
checkout to run it.

Resolve a bare command name through `command -v` before the check, and drop the
now-redundant EMCC override in ci.yml — setup-emsdk already puts emcc on PATH,
which is what the script's own default looks for.

Verified by invoking it the way CI does: `EMCC=emcc bash scripts/build-wasm.sh`
now builds. Incidentally confirms the new freshness gate is sound — the local
toolchain is the same pinned emcc 3.1.69, and the rebuild reproduced the
committed artifact byte-for-byte.

run-all-tests.sh ALL GREEN.
2026-07-21 12:14:21 +02:00
..
ci.yml fix(build): resolve a bare EMCC command name in build-wasm.sh 2026-07-21 12:14:21 +02:00
osc-bridge.yml feat(manifold)!: P1 — retire playground/, manifold is the sole browser app 2026-07-13 23:27:56 +02:00
vcv-plugin.yml build(vcv): cross-platform CI + Linux dist + /next/vcv publish flow 2026-06-28 04:49:40 +02:00