Provided by: cargo_0.47.0-1~exp1ubuntu1~16.04.1_amd64 bug


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


   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 the enabled features for the "current" package. The
       "current" package is the package in the current directory, or the one specified in
       --manifest-path. If running in the root of a virtual workspace, then the default features
       are selected for all workspace members, or all features if --all-features is specified.

       When no feature options are given, the default feature is activated for every selected

       --features FEATURES
           Space or comma separated list of features to activate. These features only apply to
           the current directory’s package. Features of direct dependencies may be enabled with
           <dep-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 current directory’s package.

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

           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 config value
           <>. 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:

           •   auto (default): Automatically detect if color support is available on the

           •   always: Always display colors.

           •   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 values:

           •   human (default): Display in a human-readable text format.

           •   short: Emit shorter, human-readable text messages.

           •   json: Emit JSON messages to stdout. See the reference
               <> for
               more details.

           •   json-diagnostic-short: Ensure the rendered field of JSON messages contains the
               "short" rendering from rustc.

           •   json-diagnostic-rendered-ansi: Ensure the rendered field of JSON messages contains
               embedded ANSI color codes for respecting rustc’s default color scheme.

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

   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.

           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

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

   Miscellaneous Options
       -j N, --jobs N
           Number of parallel jobs to run. May also be specified with the config value
           <>. Defaults to the number of


       Profiles may be used to configure compiler options such as optimization levels and debug
       settings. See the reference <> for
       more details.

       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

       │                     │                 │                   │
       │Target               │ Default Profile │ --release Profile │
       │                     │                 │                   │
       │lib, bin, example    │ devrelease           │
       │                     │                 │                   │
       │test, bench, or any  │ testbench             │
       │target               │                 │                   │
       │in "test" or "bench" │                 │                   │
       │mode                 │                 │                   │

       Dependencies use the dev/release profiles.


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


           Cargo succeeded.

           Cargo failed to complete.


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

               cargo run

        2. Run an example with extra arguments:

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


       cargo(1), cargo-build(1)

                                            2020-04-21                               CARGO-RUN(1)