rustup & Toolchain Management

rustup installs and switches Rust toolchains, components (clippy, rustfmt), and cross-compilation targets. It is the supported way to manage Rust on developer machines and CI.

Recipe

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
rustup default stable
rustup toolchain install 1.97.0
rustup component add rustfmt clippy rust-analyzer
rustup target add wasm32-unknown-unknown

When to reach for this:

• Onboarding new developers
• Pinning MSRV across team
• Adding ARM or musl targets for release builds

Working Example

# rust-toolchain.toml (repo root)
[toolchain]
channel = "1.97.0"
components = ["rustfmt", "clippy"]
targets = ["x86_64-unknown-linux-gnu"]

cd my-repo
rustc --version   # 1.97.0 via override
cargo clippy

What this demonstrates:

• rust-toolchain.toml auto-selects toolchain in directory
• Components travel with pinned channel
• CI should use same pin via dtolnay/rust-toolchain

Deep Dive

Channels

Profiles

rustup set profile minimal on CI agents; default on dev laptops includes rust-docs.

Gotchas

• Distro apt install rustc - ancient version. Fix: rustup only; remove apt rust.
• Forgot component - clippy not found. Fix: rustup component add clippy.
• Override confusion - global stable vs project 1.97. Fix: trust rust-toolchain.toml.
• WSL path mixing - Windows rustup vs Linux rustup. Fix: one environment per workflow.
• Disk usage - many toolchains fill disk. Fix: rustup toolchain list and prune old.

Alternatives

FAQs

Related

• Toolchain Setup Checklist
• Cross-compilation
• Build & inspect tooling
• CI config for Rust

Stack versions: This page was written for Rust 1.97.0 (edition 2024), Tokio 1.x, Axum 0.8, serde 1.0, sqlx 0.8, clap 4, and Polars 0.46+.