Skip to content

docs: use cargo-zigbuild for aarch64 cross-compilation#43

Merged
madeye merged 1 commit into
mainfrom
docs/zigbuild-cross-compile
Jun 14, 2026
Merged

docs: use cargo-zigbuild for aarch64 cross-compilation#43
madeye merged 1 commit into
mainfrom
docs/zigbuild-cross-compile

Conversation

@madeye

@madeye madeye commented Jun 14, 2026

Copy link
Copy Markdown
Owner

What

Replace the Docker-based cross cross-compile instructions in CLAUDE.md (Build + Deploy sections) with cargo zigbuild.

Why

cargo zigbuild uses Zig as the linker and needs no Docker, which removes the previous "must run from a Docker-mountable path (NOT /Volumes/)" restriction — builds now work directly from any checkout, including /Volumes/.... The glibc suffix (.2.31) pins the target ABI to cover Raspberry Pi OS bullseye/bookworm.

Verified working: built current main this way (~16s, no Docker) and deployed the resulting aarch64 binary to the live gateway successfully.

Notes

  • Docs-only change; no code touched.
  • Requires cargo install cargo-zigbuild + a Zig toolchain (brew install zig).

🤖 Generated with Claude Code

Replace the `cross` (Docker-based) cross-compile instructions with
`cargo zigbuild`, which uses Zig as the linker and needs no Docker.
This removes the "must run from a Docker-mountable path" restriction,
so builds work directly from /Volumes/... checkouts. Pin glibc 2.31
to match Raspberry Pi OS bullseye/bookworm.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@madeye madeye merged commit ef27121 into main Jun 14, 2026
6 checks passed
@madeye madeye deleted the docs/zigbuild-cross-compile branch June 14, 2026 04:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant