Skip to content

cargo: drop shared musl rustflags; each repo owns its rustflags #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HarryR merged 2 commits into from
Jul 9, 2026
Merged

cargo: drop shared musl rustflags; each repo owns its rustflags #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8e45a36
cargo: drop shared musl rustflags; each repo owns its rustflags
HarryR Jul 9, 2026
5597a6a
cargo: tighten the shared-config header comment
HarryR Jul 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 9 additions & 34 deletions .cargo/config.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,39 +1,14 @@
# Shared Cargo configuration for the whole Lock.Boot workspace.
# Shared Cargo configuration for the whole Lock.Boot workspace (loaded via CARGO_HOME, and via
# hierarchical discovery inside any sub-repo). It carries ONLY workspace-wide settings; rustflags and
# `[build] target` live in each repo's own .cargo/config.toml, for two reasons:
#
# Because CARGO_HOME points at this directory ($WORKSPACE/.cargo), this file is
# loaded for every cargo invocation in the workspace, AND it is picked up via
# Cargo's hierarchical config discovery when running inside any sub-repo. A
# sub-repo's own .cargo/config.toml (e.g. lockboot's) takes precedence on any
# key it sets; this file provides the shared defaults.
# - CI checks out each repo ALONE (no workspace parent, CARGO_HOME redirected), so anything a build
# needs must be in the repo, or CI and local diverge.
# - Cargo CONCATENATES `rustflags` across config files (a sub-repo's does NOT override this one), so
# defining flags both here and in a repo would double them and change the compiled bytes.
#
# NOTE: we deliberately do NOT set `[build] target` here. The house style is
# static musl, but forcing a global default target would break the gnu-host
# repos (vaportpm, the risc0 host crate in vaportpm-zk) and the Python site
# (wavebend.org). Repos that want musl-by-default set it in their own
# .cargo/config.toml (lockboot and os402 do); everyone else opts in with
# `--target x86_64-unknown-linux-musl`.
#
# We also deliberately do NOT set a linker for the gnu host target here. The
# musl flags below only bind when a musl target is actually opted into, so they
# are safe to share; but forcing e.g. `linker=rust-lld` on the default
# x86_64-unknown-linux-gnu build would apply to vaportpm and the risc0 host
# crate (which have gcc and may link C deps) - leave gnu linking to each repo.

[target.x86_64-unknown-linux-musl]
# Fully static linking with rustc's bundled musl and the built-in rust-lld
# linker (no system cc needed).
rustflags = [
"-C", "linker=rust-lld",
"-C", "target-feature=+crt-static",
"-C", "link-arg=-static",
]

[target.aarch64-unknown-linux-musl]
rustflags = [
"-C", "linker=rust-lld",
"-C", "target-feature=+crt-static",
"-C", "link-arg=-static",
]
# No `[build] target` here either: it would break the gnu-host repos (vaportpm, vaportpm-zk) and the
# Python site (wavebend.org). Musl repos set their own; gnu-host repos opt in with `--target musl`.

[env]
# Reproducible builds by default across every repo.
Expand Down