rust-toolchain.toml

Rama main · réplica de lectura del repositorio original.

# Pin the toolchain so local dev, CI release builds, and the Windows
# signing workflow all use one rustc. This is the base for attestable /
# reproducible release builds: two builds on different days can't drift
# to different compiler versions. Bump deliberately, in lockstep with a
# verified release build.
[toolchain]
channel = "1.98.0"
components = ["rustfmt", "clippy"]
targets = [
  "x86_64-unknown-linux-gnu",
  "aarch64-unknown-linux-gnu",
  "aarch64-apple-darwin",
  "x86_64-apple-darwin",
  "x86_64-pc-windows-gnu",
  # 32-bit ARM (Raspberry Pi 2/3/Zero 2 W on 32-bit Raspberry Pi OS),
  # BETA - TODO 178. musl because those images' glibc predates every
  # build host we have. Listed here so `cargo zigbuild --target
  # armv7-unknown-linux-musleabihf` works from a fresh checkout: the
  # target is where 64-bit assumptions surface (usize is 32-bit), and a
  # target nobody can build without a setup step is one nobody checks.
  "armv7-unknown-linux-musleabihf",
  # 64-bit ARM Linux, STATIC, for nightly's `aarch64-cross` job: the only
  # place gf16's plain-NEON (no sha3) dispatch runs, under qemu on a
  # Cortex-A72 model. The gnu target above is what the release tarball
  # ships; this one exists because a static binary runs under qemu-user
  # with no sysroot (the same reason the armv7 job is musl).
  "aarch64-unknown-linux-musl",
]