Damian Reeves (Feb 07 2026 at 18:37): Damian Reeves (Feb 07 2026 at 18:37):I want to use wastime-go in an application that includes windows arm64 and macos arm64 targets, however the wasmtime-go README.md makes it seem like these aren't supported or will require building wasmtime myself in order to use it, as seen in the below statement:
This Go library uses CGO to consume the C API of the Wasmtime project which is written in Rust. Precompiled binaries of Wasmtime are checked into this repository on tagged releases so you won't have to install Wasmtime locally, but it means that this project only works on Linux x86_64, macOS x86_64 , and Windows x86_64 currently. Building on other platforms will need to arrange to build Wasmtime and use
CGO_*env vars to compile correctly.
However when I look at wasmtime releases I see that wasmtime publishes these targets (and many others, including wasm targets which interest me as well what those mean).
Is the wasmtime-go README.md just outdated? Or are there still current support issues for the targets I mentioned?
Damian Reeves (Feb 07 2026 at 19:09):So if this is supported I may actually have a bigger problem as wasmtime-go doesn't seem to support the component model. Is there any timeline on when we can expect to see that?
Alex Crichton (Feb 07 2026 at 19:17):https://github.com/bytecodealliance/wasmtime-go/tree/v40.0.0/build has the architectures that are shipped right now which are currently a subset of wasmtimes architectures. Lack of inclusion is just for lack of effort mostly, and yeah I think the README is a bit outdated.
The C API has support for components but that's not implemented in Go yet. Not for any reason other than lack of effort though.
Damian Reeves (Feb 07 2026 at 19:23):So is adding the windows-aarch64 as "simple" as it seems? Just add the folder?
Alex Crichton (Feb 07 2026 at 21:29):yeah in theory it's a small edit here plus maybe a new CI job to test that it works
Last updated: Feb 24 2026 at 04:36 UTC