CARGO-RUN(1)

📦 version 1.76.0, in ubuntu jammy, ubuntu noble

💅 cargo-run — the manual, section 1, General Commands Manual 💅

okay bestie, pull up a chair 🫶 you just opened the cargo-run manpage and honestly? it's giving main character energy. let's get into it.

✨ NAME ✨

cargo-run — Run the current package 🌈

🌸 SYNOPSIS 🌸

cargo run [options] [-- args]

🦋 DESCRIPTION 🦋

Run a binary or example of the local package. that's the whole vibe. 🎀

All the arguments following the two dashes (--) are passed to the binary to run. If you're passing arguments to both Cargo and the binary, the ones after -- go to the binary, the ones before go to Cargo. it's literally a little handoff moment, so cute.

Unlike cargo-test(1) and cargo-bench(1), cargo run sets the working directory of the binary executed to the current working directory, same as if it was executed in the shell directly. no cap, it just runs it right where you're standing. 💅

✨ OPTIONS ✨

🎁 Package Selection

By default, the package in the current working directory is selected. The -p flag can be used to choose a different package in a workspace.

  • -p spec, --package spec — the package to run. See cargo-pkgid(1) for the SPEC format. 👑

🎯 Target Selection

When no target selection options are given, cargo run will run the binary target. If there are multiple binary targets, you must pass a target flag to choose one. Or, the default-run field may be specified in the [package] section of Cargo.toml to choose the name of the binary to run by default.

  • --bin name — run the specified binary. 🍓
  • --example name — run the specified example. 🌸

🧚 Feature Selection

The feature flags allow you to control which features are enabled. When no feature options are given, the default feature is activated for every selected package.

See the features documentation at https://doc.rust-lang.org/cargo/reference/features.html#command-line-feature-options for more details.

  • -F features, --features features — space or comma separated list of features to activate. Features of workspace members may be enabled with package-name/feature-name syntax. This flag may be specified multiple times, which enables all specified features. 💖
  • --all-features — activate all available features of all selected packages. go big or go home fr fr.
  • --no-default-features — do not activate the default feature of the selected packages. 🙈

🔥 Compilation Options

  • --target triple — run for the given architecture. The default is the host architecture. The general format of the triple is <arch><sub>-<vendor>-<sys>-<abi>. Run rustc --print target-list for a list of supported targets.

This may also be specified with the build.target config value at https://doc.rust-lang.org/cargo/reference/config.html.

Note that specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation at https://doc.rust-lang.org/cargo/guide/build-cache.html for more details. 🫶
  • -r, --release — run optimized artifacts with the release profile. See also the --profile option for choosing a specific profile by name. ✨
  • --profile name — run with the given profile. See the reference at https://doc.rust-lang.org/cargo/reference/profiles.html for more details on profiles.
  • --ignore-rust-version — run the target even if the selected Rust compiler is older than the required Rust version as configured in the project's rust-version field. living dangerously, love that for you.
  • --timings=fmts — output information how long each compilation takes, and track concurrency information over time. Accepts an optional comma-separated list of output formats; --timings without an argument will default to --timings=html. Specifying an output format (rather than the default) is unstable and requires -Zunstable-options. Valid output formats:
    • html (unstable, requires -Zunstable-options): write a human-readable file cargo-timing.html to the target/cargo-timings directory with a report of the compilation. Also write a report to the same directory with a timestamp in the filename if you want to look at older runs. HTML output is suitable for human consumption only, and does not provide machine-readable timing data. 🎀
    • json (unstable, requires -Zunstable-options): emit machine-readable JSON information about timing information. 🤖

📦 Output Options

  • --target-dir directory — directory for all generated artifacts and intermediate files. May also be specified with the CARGO_TARGET_DIR environment variable, or the build.target-dir config value at https://doc.rust-lang.org/cargo/reference/config.html. Defaults to target in the root of the workspace. 💜

👀 Display Options

  • -v, --verbose — use verbose output. May be specified twice for "very verbose" output which includes extra output such as dependency warnings and build script output. May also be specified with the term.verbose config value at https://doc.rust-lang.org/cargo/reference/config.html. tell me everything bestie 🗣️
  • -q, --quiet — do not print cargo log messages. May also be specified with the term.quiet config value at https://doc.rust-lang.org/cargo/reference/config.html. 🤫
  • --color when — control when colored output is used. Valid values:
    • auto (default): automatically detect if color support is available on the terminal.
    • always: always display colors. 🌈
    • never: never display colors. 💀

May also be specified with the term.color config value at https://doc.rust-lang.org/cargo/reference/config.html.

  • --message-format fmt — the output format for diagnostic messages. Can be specified multiple times and consists of comma-separated values. Valid values:
    • human (default): display in a human-readable text format. Conflicts with short and json.
    • short: emit shorter, human-readable text messages. Conflicts with human and json.
    • json: emit JSON messages to stdout. See the reference at https://doc.rust-lang.org/cargo/reference/external-tools.html#json-messages for more details. Conflicts with human and short.
    • json-diagnostic-short: ensure the rendered field of JSON messages contains the "short" rendering from rustc. Cannot be used with human or short.
    • json-diagnostic-rendered-ansi: ensure the rendered field of JSON messages contains embedded ANSI color codes for respecting rustc's default color scheme. Cannot be used with human or short.
    • json-render-diagnostics: instruct Cargo to not include rustc diagnostics in JSON messages printed, but instead Cargo itself should render the JSON diagnostics coming from rustc. Cargo's own JSON diagnostics and others coming from rustc are still emitted. Cannot be used with human or short.

📜 Manifest Options

  • --manifest-path path — path to the Cargo.toml file. By default, Cargo searches for the Cargo.toml file in the current directory or any parent directory. 🔍
  • --frozen, --locked — either of these flags requires that the Cargo.lock file is up-to-date. If the lock file is missing, or it needs to be updated, Cargo will exit with an error. The --frozen flag also prevents Cargo from attempting to access the network to determine if it is out-of-date.

These may be used in environments where you want to assert that the Cargo.lock file is up-to-date (such as a CI build) or want to avoid network access. no surprises allowed, periodt.

  • --offline — prevents Cargo from accessing the network for any reason. Without this flag, Cargo will stop with an error if it needs to access the network and the network is not available. With this flag, Cargo will attempt to proceed without the network if possible.
Beware that this may result in different dependency resolution than online mode. Cargo will restrict itself to crates that are downloaded locally, even if there might be a newer version as indicated in the local copy of the index. See the cargo-fetch(1) command to download dependencies before going offline. ⚠️

May also be specified with the net.offline config value at https://doc.rust-lang.org/cargo/reference/config.html.

🌟 Common Options

  • +toolchain — if Cargo has been installed with rustup, and the first argument to cargo begins with +, it will be interpreted as a rustup toolchain name (such as +stable or +nightly). See the rustup documentation at https://rust-lang.github.io/rustup/overrides.html for more information about how toolchain overrides work.
  • --config KEY=VALUE or PATH — overrides a Cargo configuration value. The argument should be in TOML syntax of KEY=VALUE, or provided as a path to an extra configuration file. This flag may be specified multiple times. See the command-line overrides section at https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides for more information.
  • -C PATH — changes the current working directory before executing any specified operations. This affects things like where cargo looks by default for the project manifest (Cargo.toml), as well as the directories searched for discovering .cargo/config.toml, for example. This option must appear before the command name, for example cargo -C path/to/my-project build.
This option is only available on the nightly channel at https://doc.rust-lang.org/book/appendix-07-nightly-rust.html and requires the -Z unstable-options flag to enable (see #10098 at https://github.com/rust-lang/cargo/issues/10098). 🌙
  • -h, --help — prints help information. 🫶
  • -Z flag — unstable (nightly-only) flags to Cargo. Run cargo -Z help for details. 🔥

🎀 Miscellaneous Options

  • -j N, --jobs N — number of parallel jobs to run. May also be specified with the build.jobs config value at https://doc.rust-lang.org/cargo/reference/config.html. Defaults to the number of logical CPUs. If negative, it sets the maximum number of parallel jobs to the number of logical CPUs plus provided value. If a string default is provided, it sets the value back to defaults. Should not be 0. 🚫
  • --keep-going — build as many crates in the dependency graph as possible, rather than aborting the build on the first one that fails to build.

For example if the current package depends on dependencies fails and works, one of which fails to build, cargo run -j1 may or may not build the one that succeeds (depending on which one of the two builds Cargo picked to run first), whereas cargo run -j1 --keep-going would definitely run both builds, even if the one run first fails. 💪

🌈 ENVIRONMENT 🌈

See the reference at https://doc.rust-lang.org/cargo/reference/environment-variables.html for details on environment variables that Cargo reads. 👑

💀 EXIT STATUS 💀

okay bestie, when the command is done doing its lil thing, it tells you how it went with a number. here's the tea:

  • 0 — Cargo succeeded. slay!! it worked, we ate, no notes 💅
  • 101 — Cargo failed to complete. not iconic. something went wrong, bestie 😭

✨ EXAMPLES ✨

here's the vibes in action, fr fr. copy these, they're literally correct:

  1. build the local package and run its main target (assuming only one binary):
cargo run

that's it. that's the whole thing. just cargo run and your main character binary goes 🏃✨

  1. run an example with extra arguments:
cargo run --example exname -- --exoption exarg1 exarg2

peep the double dash -- — everything after it goes straight to your program, not to cargo. it's giving "hands off, this is mine" 🫶 and then exoption, exarg1, exarg2 are the args your example actually receives.

heads up: those example args (exname, exoption, exarg1, exarg2) are just placeholders bestie — swap in your own 🎀

🌈 SEE ALSO 🌈

go read these next, they're the whole friend group:

  • cargo(1) — the main character, the mothership 👑
  • cargo-build(1) — for when you wanna build without the running part 🦋

that's the whole page bestie, you made it to the end 🎉 this was CARGO-RUN(1), straight out of the Cargo manual — go run something iconic with it, ily, mwah 💖✨🎀

📦 where this page comes from