Until Go 1.23, the Go compiler always generated ARM64 binaries that could be executed by any ARMv8-A processor. Go 1.23 introduced a new GOARM64 environment variable, which specifies the …

Starting from Go 1.1, the appropriate GOARM value will be chosen if you compile the program from source on the target machine. In cross compilation situations, it is recommended that you always set …

For some architectures, Go supports compiling to specific microarchitectures using environment variables, e.g. GOAMD64 for go1.18 and later. Binaries will check at startup whether the requested …

Feb 6, 2018 · For some architectures, Go supports compiling to specific microarchitectures using environment variables, e.g. GOAMD64 for go1.18 and later. Binaries will check at startup whether …

To generate a fat XCFramework that supports iOS, macOS, and macCatalyst for all supportec architectures (amd64 and arm64), specify -target ios,macos,maccatalyst.

Jun 2, 2026 · Use GOOS, GOARCH, and CGO_ENABLED to produce reproducible Go binaries for every target you ship to — from amd64 Linux to ARM64 Graviton.

Jan 16, 2026 · CGO requires a target-specific C compiler, system libraries, and toolchains, which vary drastically between architectures like `arm64` (e.g., Apple M1/M2 Macs) and `amd64` (x86-64). This …

Jul 23, 2018 · I had a similar problem when I needed to build a static Go binary with cgo that would eventually run in an alpine container with arm64 architecture, but had to be built in a golang:alpine …

Jan 19, 2021 · I need to compilet a go library via C to a DLL that can be used through PInvoke on ARM/ARM64 Windows. I find many open issues, topics and discussions about this and it sounds like …

Sep 16, 2025 · Compiling Go code for a different architecture like ARM is straightforward thanks to Go's built-in cross-compilation support. You don't need a separate compiler or toolchain—just set a few …