How do you cross-compile a Go binary for Linux from a macOS machine?

Q: How do you cross-compile a Go binary for Linux from a macOS machine?

# Linux AMD64 (most common for servers) GOOS=linux GOARCH=amd64 go build -o bin/server ./cmd/server # Linux ARM64 (AWS Graviton, Apple M1 servers) GOOS=linux GOARCH=arm64 go build -o bin/server-arm ./cmd/server # Windows GOOS=windows GOARCH=amd64 go build -o bin/server.exe ./cmd/server # List all supported targets go tool dist list # CGo disables cross-compilation — use CGO_ENABLED=0 for pure Go CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build \ -ldflags='-w -s' \ -o bin/server ./cmd/server # -w: omit DWARF debug info # -s: omit symbol table # Together reduce binary size by ~30% # Multi-arch Docker image with buildx docker buildx build \ --platform linux/amd64,linux/arm64 \ -t myregistry/myservice:latest \ --push . CGO_ENABLED=0 produces a fully static binary — required for FROM scratch Docker images CGo complicates cross-compilation — use Docker buildx for services that require CGo GOARM=7 for 32-bit ARM (Raspberry Pi) alongside GOARCH=arm Version the binary with ldflags: -ldflags "-X main.version=$(git describe --tags)" Use goreleaser for automating multi-platform releases with changelogs and checksums

Difficulty: 5/10

cross-compilation, environment variables, build flags

Set GOOS and GOARCH environment variables before go build. Go's toolchain includes full cross-compilation support with no separate toolchain needed for pure Go code.

Cross-compilation examples

Cross-compilation considerations

1
CGO_ENABLED=0 produces a fully static binary — required for FROM scratch Docker images
2
CGo complicates cross-compilation — use Docker buildx for services that require CGo
3

How do you cross-compile a Go binary for Linux from a macOS machine?

Difficulty: 5/10

cross-compilation, environment variables, build flags

Set GOOS and GOARCH environment variables before go build. Go's toolchain includes full cross-compilation support with no separate toolchain needed for pure Go code.

Cross-compilation examples

Cross-compilation considerations

1
CGO_ENABLED=0 produces a fully static binary — required for FROM scratch Docker images
2
CGo complicates cross-compilation — use Docker buildx for services that require CGo
3

How do you cross-compile a Go binary for Linux from a macOS machine?

Set GOOS and GOARCH environment variables before go build. Go's toolchain includes full cross-compilation support with no separate toolchain needed for pure Go code.

How do you cross-compile a Go binary for Linux from a macOS machine?

Set GOOS and GOARCH environment variables before go build. Go's toolchain includes full cross-compilation support with no separate toolchain needed for pure Go code.

Scenario Questions

Follow-up Questions