cargo-run - Run the current package
cargo run [options] [-- args]
Run a binary or example of the local package.
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
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
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.
Run the specified binary.
Run the specified example.
The feature flags allow you to control which features are enabled. When no
feature options are given, the default feature is activated for every
See the features documentation
for more details.
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.
Activate all available features of all selected
Do not activate the default feature of the
Run for the given architecture. The default is the host
architecture. The general format of the triple is
rustc --print target-list
for a list of supported targets.
This may also be specified with the build.target config
Note that specifying this flag makes Cargo run in a different mode
where the target artifacts are placed in a separate directory. See the
for more details.
Run optimized artifacts with the release profile.
See the PROFILES section for details on how this affects profile
Directory for all generated artifacts and intermediate
files. May also be specified with the CARGO_TARGET_DIR
variable, or the build.target-dir config value
. Defaults to
in the root of the workspace.
No output printed to stdout.
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
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-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
•json-render-diagnostics: Instruct Cargo to
not include rustc diagnostics in 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.
Path to the Cargo.toml file. By default, Cargo
searches for the Cargo.toml file in the current directory or any parent
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.
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
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
). See the
for more information
about how toolchain overrides work.
Prints help information.
Unstable (nightly-only) flags to Cargo. Run cargo -Z
help for details.
Profiles may be used to configure compiler options such as optimization levels
and debug settings. See the reference
https://doc.rust-lang.org/cargo/reference/profiles.html for more
Profile selection depends on the target and crate being built. By
default the dev or test profiles are used. If the
--release flag is given, then the release or bench
profiles are used.
|lib, bin, example
|test, bench, or any target in
"test" or "bench" mode
Dependencies use the dev/release profiles.
•0: Cargo succeeded.
•101: Cargo failed to complete.
1.Build the local package and run its main target
(assuming only one binary):
2.Run an example with extra arguments:
cargo run --example exname -- --exoption exarg1 exarg2