tygor-toolchain

Prebuilt toolchain archives that the tygor CLI downloads, so users need only Go to build browser apps.

Wasm-only TinyGo 0.42.0

Release toolchain-tinygo-wasm-0.42.0-r1:

Platform	Asset	Bytes	SHA-256
linux-amd64	tinygo0.42.0.wasm-only.linux-amd64.tar.xz	32621268	75fb5992d31d42b0725a75ddd8c68f2b22380052e886d3d578273882065572ce
linux-arm64	tinygo0.42.0.wasm-only.linux-arm64.tar.xz	28810260	0df884c40326904c639347b0e0774f305449b285b95139e9eb59d159db0d7653
darwin-amd64	tinygo0.42.0.wasm-only.darwin-amd64.tar.xz	32800528	29b081fca39b989626851dbe8af2acc6e8847eb1a3f5f6dd3155aac1b706e5a5
darwin-arm64	tinygo0.42.0.wasm-only.darwin-arm64.tar.xz	29101428	ed7e321208578dc94be739b2adf24647869a7a50b8014649878effe0d54cb7cd

Each archive is TinyGo v0.42.0 (bdc4a21a) built against its pinned LLVM (2be7242b) with only the WebAssembly backend and the wasm-ld linker, plus the upstream release's src, lib/clang, lib/compiler-rt-builtins, lib/wasi-libc and wasm target files. That is about 30 MB, against 165 to 185 MB for the full upstream release. It compiles only -target wasm.

Every asset has a .provenance.txt sidecar: source revisions, upstream archive hash, builder script hash, invocation, build paths, CMake configuration and host tool versions. verification.txt records the Darwin repeatability and counter-Wasm checks.

Rebuild

tinygo-wasm/ holds the builders and the checksum manifest:

tinygo-wasm/build-tinygo-wasm-linux.sh amd64 WORKDIR OUT.tar.xz    # Debian 12; arm64 cross-builds too
tinygo-wasm/build-tinygo-wasm-darwin.sh arm64 WORKDIR OUT.tar.xz   # macOS; amd64 cross-builds on arm64
sha256sum -c tinygo-wasm/tinygo-wasm-0.42.0-r1.sha256

The output bytes are repeatable for the same host toolchain and the same build paths; the provenance sidecars record both. A different host or path gives a working archive with a different hash.

License

TinyGo is BSD-3-Clause (tinygo/LICENSE in each archive). LLVM, Clang and LLD are Apache-2.0 with LLVM exceptions. wasi-libc and compiler-rt keep their upstream licenses.