Explain why gcc-arm-linux-gnueabihf is installed for musleabihf builds:
- Pure arm-linux-musleabihf-gcc not available in standard repos
- Use gnueabihf linker as tool with Rust target spec
- Static linking via -C link-arg=-static produces portable musl binary
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add build time comparison (native vs cross-compile)
- Note that .cargo/config.toml is now included in repo
- Add static linking benefits table
- Include verification commands for static binaries
- Add cross-platform prerequisites (Linux, macOS, Windows)
- Add workflow diagram for cross-compilation process
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add comprehensive step-by-step guide for compiling ZeroClaw on
Raspberry Pi Zero W (512MB RAM, ARMv6). Includes:
- Target ABI comparison (gnueabihf vs musleabihf)
- Native compilation instructions with swap setup
- Cross-compilation from more powerful hosts
- systemd service configuration
- Troubleshooting for constrained devices
musleabihf is recommended for smaller static binaries and better
portability across Raspberry Pi OS versions.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
