Go to main content

man pages section 1: User Commands

Exit Print View

Updated: Wednesday, July 27, 2022

cargo-run (1)


cargo-run - Run the current package


cargo run [options] [-- args]


CARGO-RUN(1)                General Commands Manual               CARGO-RUN(1)

       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

   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
       for more details.

       --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.

           Activate all available features of all selected packages.

           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

           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 for more details.

           Run optimized artifacts with the release profile. See the PROFILES
           section for details on how this affects profile selection.

   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
           <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

       -q, --quiet
           No output printed to stdout.

       --color when
           Control when colored output is used. Valid values:

           o  auto (default): Automatically detect if color support is
               available on the terminal.

           o  always: Always display colors.

           o  never: Never display colors.

           May also be specified with the term.color config value

       --message-format fmt
           The output format for diagnostic messages. Can be specified
           multiple times and consists of comma-separated values. Valid

           o  human (default): Display in a human-readable text format.
               Conflicts with short and json.

           o  short: Emit shorter, human-readable text messages. Conflicts
               with human and json.

           o  json: Emit JSON messages to stdout. See the reference
               for more details. Conflicts with human and short.

           o  json-diagnostic-short: Ensure the rendered field of JSON
               messages contains the "short" rendering from rustc. Cannot be
               used with human or short.

           o  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

           o  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.

   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

           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 value

   Common Options
           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
           <https://rust-lang.github.io/rustup/overrides.html> for more
           information about how toolchain overrides work.

       -h, --help
           Prints help information.

       -Z flag
           Unstable (nightly-only) flags to Cargo. Run cargo -Z help for

   Miscellaneous Options
       -j N, --jobs N
           Number of parallel jobs to run. May also be specified with the
           build.jobs config value
           <https://doc.rust-lang.org/cargo/reference/config.html>. Defaults
           to the number of CPUs.

       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.

       |Target              | Default Profile | --release Profile |
       |lib, bin, example   | dev             | release           |
       |test, bench, or any | test            | bench             |
       |target in "test" or |                 |                   |
       |"bench" mode        |                 |                   |

       Dependencies use the dev/release profiles.

       See the reference
       for details on environment variables that Cargo reads.

       o  0: Cargo succeeded.

       o  101: Cargo failed to complete.

        1. Build the local package and run its main target (assuming only one

               cargo run

        2. Run an example with extra arguments:

               cargo run --example exname -- --exoption exarg1 exarg2

       See attributes(7) for descriptions of the following attributes:

       |Availability   | developer/rust/cargo |
       |Stability      | Volatile             |

       cargo(1), cargo-build(1)

       Source code for open source software components in Oracle Solaris can
       be found at https://www.oracle.com/downloads/opensource/solaris-source-

       This software was built from source available at
       https://github.com/oracle/solaris-userland. The original community
       source was downloaded from  https://static.rust-

       Further information about this software can be found on the open source
       community website at http://www.rust-lang.org/.