diff --git a/crates/mdman/doc/out/mdman.md b/crates/mdman/doc/out/mdman.md index aefafa48bbd..08233ac3224 100644 --- a/crates/mdman/doc/out/mdman.md +++ b/crates/mdman/doc/out/mdman.md @@ -53,7 +53,7 @@ man page:
-t type-t typeSpecifies the output type. The following output types are supported:
man — A troff-style man page. Outputs with a numbered extension (like
@@ -66,18 +66,18 @@ available. Outputs with the .txt extension.-o outdir-o outdirSpecifies the directory where to save the output.
--url base_url--url base_urlSpecifies a base URL to use for relative URLs within the document. Any relative URL will be joined with this URL.
--man name:section=url--man name:section=urlSpecifies a URL to use for the given man page. When the {{man name section}} expression is used, the given URL will be inserted as a link. This
may be specified multiple times. If a man page reference does not have a
matching --man entry, then a relative link to a file named name.md will
@@ -85,7 +85,7 @@ be used.
The source input filename, may be specified multiple times.
--include--includeTesting an included link.
--foo-bar--foo-barExample link. See other-cmd(1), local-cmd(1)
--foo-bar--foo-barDemo emphasis, strong, strike
-p spec--package spec-p spec--package specThis has multiple flags.
A named argument.
--complex--complexThis option has a list.
@filename@filenameLoad from filename.
--foo [bar]--foo [bar]Flag with optional value.
--foo[=bar]--foo[=bar]Alternate syntax for optional value (with required = for disambiguation).
--split-block--split-blockAn option where the description has a block statement that is split across multiple lines
--git url--git url--branch branch--branch branchBranch to use when adding from git.
--tag tag--tag tagTag to use when adding from git.
--rev sha--rev shaSpecific commit to use when adding from git.
--path path--path pathFilesystem path to local crate to add.
--base base--base baseThe path base to use when adding a local crate.
--registry registry--registry registryName of the registry to use. Registry names are defined in Cargo config
files. If not specified, the default registry is used,
which is defined by the registry.default config key which defaults to
@@ -84,17 +84,17 @@ which is defined by the registry.default config key which defaults
--dev--devAdd as a development dependency.
--build--buildAdd as a build dependency.
--target target--target targetAdd as a dependency to the given target platform.
To avoid unexpected shell expansions, you may use quotes around each target, e.g., --target 'cfg(unix)'.
registry.default config key which defaults
--dry-run--dry-runDon’t actually write the manifest
--rename name--rename nameRename the dependency.
--optional--optionalMark the dependency as optional.
--no-optional--no-optionalMark the dependency as required.
--public--publicMark the dependency as public.
The dependency can be referenced in your library’s public API.
--no-public--no-publicMark the dependency as private.
While you can use the crate in your implementation, it cannot be referenced in your public API.
--no-default-features--no-default-featuresDisable the default features.
--default-features--default-featuresRe-enable the default features.
-F features--features features-F features--features featuresSpace or comma separated list of features to activate. When adding multiple crates, the features for a specific crate may be enabled with @@ -166,8 +166,8 @@ which enables all specified features.
### Display Options-v--verbose-v--verboseUse 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
@@ -175,15 +175,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -200,24 +200,24 @@ terminal.--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
-p spec--package spec-p spec--package specAdd dependencies to only the specified package.
--ignore-rust-version--ignore-rust-versionIgnore rust-version specification in packages.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -244,12 +244,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -267,7 +267,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -276,14 +276,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -295,13 +295,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--no-run--no-runCompile, but don’t run benchmarks.
--no-fail-fast--no-fail-fastRun all benchmarks regardless of failure. Without this flag, Cargo will exit after the first executable fails. The Rust test harness will run all benchmarks within the executable to completion, this flag only applies to the executable @@ -96,8 +96,8 @@ virtual workspace will include all workspace members (equivalent to passing
-p spec…--package spec…-p spec…--package spec…Benchmark only the specified packages. See cargo-pkgid(1) for the
SPEC format. This flag may be specified multiple times and supports common Unix
glob patterns like *, ? and []. However, to avoid your shell accidentally
@@ -106,17 +106,17 @@ double quotes around each pattern.
--workspace--workspaceBenchmark all members in the workspace.
--all--allDeprecated alias for --workspace.
--exclude SPEC…--exclude SPEC…Exclude the specified packages. Must be used in conjunction with the
--workspace flag. This flag may be specified multiple times and supports
common Unix glob patterns like *, ? and []. However, to avoid your shell
@@ -171,40 +171,40 @@ use single quotes or double quotes around each glob pattern.
--lib--libBenchmark the package’s library.
--bin name…--bin name…Benchmark the specified binary. This flag may be specified multiple times and supports common Unix glob patterns.
--bins--binsBenchmark all binary targets.
--example name…--example name…Benchmark the specified example. This flag may be specified multiple times and supports common Unix glob patterns.
--examples--examplesBenchmark all example targets.
--test name…--test name…Benchmark the specified integration test. This flag may be specified multiple times and supports common Unix glob patterns.
--tests--testsBenchmark all targets that have the test = true manifest
flag set. By default this includes the library and binaries built as
unittests, and integration tests. Be aware that this will also build any
@@ -215,13 +215,13 @@ manifest settings for the target.
--bench name…--bench name…Benchmark the specified benchmark. This flag may be specified multiple times and supports common Unix glob patterns.
--benches--benchesBenchmark all targets that have the bench = true
manifest flag set. By default this includes the library and binaries built
as benchmarks, and bench targets. Be aware that this will also build any
@@ -232,7 +232,7 @@ manifest settings for the target.
--all-targets--all-targetsBenchmark all targets. This is equivalent to specifying --lib --bins --tests --benches --examples.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
--target triple--target tripleBenchmark for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -290,13 +290,13 @@ target artifacts are placed in a separate directory. See the--profile name--profile nameBenchmark with the given profile. See the reference for more details on profiles.
--timings=fmts--timings=fmtsOutput 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.
@@ -320,7 +320,7 @@ information about timing information.
### Output Options
--target-dir directory--target-dir directoryDirectory 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.
@@ -339,8 +339,8 @@ passing `--no-capture` to the benchmark binaries:
-v--verbose-v--verboseUse 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
@@ -348,15 +348,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -369,7 +369,7 @@ terminal.--message-format fmt--message-format fmtThe output format for diagnostic messages. Can be specified multiple times and consists of comma-separated values. Valid values:
human or <
### Manifest Options
--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--ignore-rust-version--ignore-rust-versionIgnore rust-version specification in packages.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -436,12 +436,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -459,7 +459,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -468,14 +468,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -487,13 +487,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
-j N--jobs N-j N--jobs NNumber of parallel jobs to run. May also be specified with the
build.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
diff --git a/src/doc/src/commands/cargo-build.md b/src/doc/src/commands/cargo-build.md
index c072b054930..2753873b8d5 100644
--- a/src/doc/src/commands/cargo-build.md
+++ b/src/doc/src/commands/cargo-build.md
@@ -28,8 +28,8 @@ virtual workspace will include all workspace members (equivalent to passing
-p spec…--package spec…-p spec…--package spec…Build only the specified packages. See cargo-pkgid(1) for the
SPEC format. This flag may be specified multiple times and supports common Unix
glob patterns like *, ? and []. However, to avoid your shell accidentally
@@ -38,17 +38,17 @@ double quotes around each pattern.
--workspace--workspaceBuild all members in the workspace.
--all--allDeprecated alias for --workspace.
--exclude SPEC…--exclude SPEC…Exclude the specified packages. Must be used in conjunction with the
--workspace flag. This flag may be specified multiple times and supports
common Unix glob patterns like *, ? and []. However, to avoid your shell
@@ -84,40 +84,40 @@ use single quotes or double quotes around each glob pattern.
--lib--libBuild the package’s library.
--bin name…--bin name…Build the specified binary. This flag may be specified multiple times and supports common Unix glob patterns.
--bins--binsBuild all binary targets.
--example name…--example name…Build the specified example. This flag may be specified multiple times and supports common Unix glob patterns.
--examples--examplesBuild all example targets.
--test name…--test name…Build the specified integration test. This flag may be specified multiple times and supports common Unix glob patterns.
--tests--testsBuild all targets that have the test = true manifest
flag set. By default this includes the library and binaries built as
unittests, and integration tests. Be aware that this will also build any
@@ -128,13 +128,13 @@ manifest settings for the target.
--bench name…--bench name…Build the specified benchmark. This flag may be specified multiple times and supports common Unix glob patterns.
--benches--benchesBuild all targets that have the bench = true
manifest flag set. By default this includes the library and binaries built
as benchmarks, and bench targets. Be aware that this will also build any
@@ -145,7 +145,7 @@ manifest settings for the target.
--all-targets--all-targetsBuild all targets. This is equivalent to specifying --lib --bins --tests --benches --examples.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
--target triple--target tripleBuild for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -203,20 +203,20 @@ target artifacts are placed in a separate directory. See the-r--release-r--releaseBuild optimized artifacts with the release profile.
See also the --profile option for choosing a specific profile by name.
--profile name--profile nameBuild with the given profile. See the reference for more details on profiles.
--timings=fmts--timings=fmtsOutput 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.
@@ -240,7 +240,7 @@ information about timing information.
### Output Options
--target-dir directory--target-dir directoryDirectory 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.
@@ -248,7 +248,7 @@ Defaults to target in the root of the workspace.
--artifact-dir directory--artifact-dir directoryCopy final artifacts to this directory.
This option is unstable and available only on the
nightly channel
@@ -262,8 +262,8 @@ See https://github.com/
### Display Options
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 Do not print cargo log messages.
May also be specified with the Control when colored output is used. Valid values: The output format for diagnostic messages. Can be specified multiple times
and consists of comma-separated values. Valid values: Outputs a series of JSON messages to stdout that indicate the commands to run
the build. This option is unstable and available only on the
@@ -330,18 +330,18 @@ See https://github.com/
### Manifest Options
Path to the Ignore Asserts that the exact same dependencies and versions are used as when the
existing 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
@@ -368,12 +368,12 @@ offline. Equivalent to specifying both Changes the path of the lockfile from the default ( If Cargo has been installed with rustup, and the first argument to Overrides a Cargo configuration value. The argument should be in TOML syntax of Changes the current working directory before executing any specified operations. This affects
things like where cargo looks by default for the project manifest ( Prints help information. Unstable (nightly-only) flags to Cargo. Run Number of parallel jobs to run. May also be specified with the
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 Displays a future-incompat report for any future-incompatible warnings
produced during execution of this command See cargo-report(1) Check only the specified packages. See cargo-pkgid(1) for the
SPEC format. This flag may be specified multiple times and supports common Unix
glob patterns like Check all members in the workspace. Deprecated alias for Exclude the specified packages. Must be used in conjunction with the
Check the package’s library. Check the specified binary. This flag may be specified multiple times
and supports common Unix glob patterns. Check all binary targets. Check the specified example. This flag may be specified multiple times
and supports common Unix glob patterns. Check all example targets. Check the specified integration test. This flag may be specified
multiple times and supports common Unix glob patterns. Check all targets that have the Check the specified benchmark. This flag may be specified multiple
times and supports common Unix glob patterns. Check all targets that have the Check all targets. This is equivalent to specifying Space or comma separated list of features to activate. Features of workspace
members may be enabled with Activate all available features of all selected packages. Do not activate the
-
-v--verbose-v--verboseterm.verbose
@@ -271,15 +271,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietterm.quiet
config value.--color when--color when
auto (default): Automatically detect if color support is available on the
@@ -292,7 +292,7 @@ terminal.--message-format fmt--message-format fmt
@@ -316,7 +316,7 @@ coming from rustc are still emitted. Cannot be used with
human or <
--build-plan--build-plan
-
--manifest-path path--manifest-path pathCargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.--ignore-rust-version--ignore-rust-versionrust-version specification in packages.--locked--lockedCargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:--offline--offline--frozen--frozen--locked and --offline.--lockfile-path PATH--lockfile-path PATH<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -391,7 +391,7 @@ requires the -Z unstable-options flag to enable (see
-
+toolchain+toolchaincargo
begins with +, it will be interpreted as a rustup toolchain name (such
as +stable or +nightly).
@@ -400,14 +400,14 @@ for more information about how toolchain overrides work.--config KEY=VALUE or PATH--config KEY=VALUE or PATHKEY=VALUE,
or provided as a path to an extra configuration file. This flag may be specified multiple times.
See the command-line overrides section for more information.-C PATH-C PATHCargo.toml), as well as
the directories searched for discovering .cargo/config.toml, for example. This option must
@@ -419,13 +419,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--help-Z flag-Z flagcargo -Z help for details.-Z unstable-options flag to enable (see
### Miscellaneous Options
-
-j N--jobs N-j N--jobs Nbuild.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
@@ -445,7 +445,7 @@ a string default is provided, it sets the value back to defaults.
Should not be 0.--keep-going--keep-goingfails and works,
@@ -455,7 +455,7 @@ first), whereas cargo build -j1 --keep-going would definitely run b
builds, even if the one run first fails.--future-incompat-report--future-incompat-report
-
-p spec…--package spec…-p spec…--package spec…*, ? and []. However, to avoid your shell accidentally
@@ -43,17 +43,17 @@ double quotes around each pattern.--workspace--workspace--all--all--workspace.--exclude SPEC…--exclude SPEC…--workspace flag. This flag may be specified multiple times and supports
common Unix glob patterns like *, ? and []. However, to avoid your shell
@@ -80,40 +80,40 @@ use single quotes or double quotes around each glob pattern.
-
--lib--lib--bin name…--bin name…--bins--bins--example name…--example name…--examples--examples--test name…--test name…--tests--teststest = true manifest
flag set. By default this includes the library and binaries built as
unittests, and integration tests. Be aware that this will also build any
@@ -124,13 +124,13 @@ manifest settings for the target.--bench name…--bench name…--benches--benchesbench = true
manifest flag set. By default this includes the library and binaries built
as benchmarks, and bench targets. Be aware that this will also build any
@@ -141,7 +141,7 @@ manifest settings for the target.--all-targets--all-targets--lib --bins --tests --benches --examples.
-
-F features--features features-F features--features featurespackage-name/feature-name syntax. This flag may
be specified multiple times, which enables all specified features.--all-features--all-features--no-default-features--no-default-featuresdefault feature of the selected packages.
--target triple--target tripleCheck for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -199,14 +199,14 @@ target artifacts are placed in a separate directory. See the-r--release-r--releaseCheck optimized artifacts with the release profile.
See also the --profile option for choosing a specific profile by name.
--profile name--profile nameCheck with the given profile.
As a special case, specifying the test profile will also enable checking in
test mode which will enable checking tests and enable the test cfg option.
@@ -216,7 +216,7 @@ detail.
--timings=fmts--timings=fmtsOutput 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.
@@ -240,7 +240,7 @@ information about timing information.
### Output Options
--target-dir directory--target-dir directoryDirectory 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.
@@ -252,8 +252,8 @@ Defaults to target in the root of the workspace.
-v--verbose-v--verboseUse 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
@@ -261,15 +261,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -282,7 +282,7 @@ terminal.--message-format fmt--message-format fmtThe output format for diagnostic messages. Can be specified multiple times and consists of comma-separated values. Valid values:
human or <
### Manifest Options
--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--ignore-rust-version--ignore-rust-versionIgnore rust-version specification in packages.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -348,12 +348,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -371,7 +371,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -380,14 +380,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -399,13 +399,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
-Z unstable-options flag to enable (see
### Miscellaneous Options
-j N--jobs N-j N--jobs NNumber of parallel jobs to run. May also be specified with the
build.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
@@ -425,7 +425,7 @@ a string default is provided, it sets the value back to defaults.
Should not be 0.
--keep-going--keep-goingBuild 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,
@@ -435,7 +435,7 @@ first), whereas cargo check -j1 --keep-going would definitely run b
builds, even if the one run first fails.
--future-incompat-report--future-incompat-reportDisplays a future-incompat report for any future-incompatible warnings produced during execution of this command
See cargo-report(1)
diff --git a/src/doc/src/commands/cargo-clean.md b/src/doc/src/commands/cargo-clean.md index 8fe0a64c339..e1e91e8c389 100644 --- a/src/doc/src/commands/cargo-clean.md +++ b/src/doc/src/commands/cargo-clean.md @@ -22,8 +22,8 @@ When no packages are selected, all packages and all dependencies in the workspace are cleaned.-p spec…--package spec…-p spec…--package spec…Clean only the specified packages. This flag may be specified multiple times. See cargo-pkgid(1) for the SPEC format.
--dry-run--dry-runDisplays a summary of what would be deleted without deleting anything.
Use with --verbose to display the actual files that would be deleted.
--doc--docThis option will cause cargo clean to remove only the doc directory in
the target directory.
--release--releaseRemove all artifacts in the release directory.
--profile name--profile nameRemove all artifacts in the directory with the given profile name.
--target-dir directory--target-dir directoryDirectory 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.
@@ -64,7 +64,7 @@ Defaults to target in the root of the workspace.
--target triple--target tripleClean for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -85,8 +85,8 @@ target artifacts are placed in a separate directory. See the ### Display Options-v--verbose-v--verboseUse 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
@@ -94,15 +94,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -119,13 +119,13 @@ terminal.--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -152,12 +152,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -175,7 +175,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -184,14 +184,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -203,13 +203,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--open--openOpen the docs in a browser after building them. This will use your default
browser unless you define another one in the BROWSER environment variable
or use the doc.browser configuration
@@ -28,12 +28,12 @@ option.
--no-deps--no-depsDo not build documentation for dependencies.
--document-private-items--document-private-itemsInclude non-public items in the documentation. This will be enabled by default if documenting a binary target.
-p spec…--package spec…-p spec…--package spec…Document only the specified packages. See cargo-pkgid(1) for the
SPEC format. This flag may be specified multiple times and supports common Unix
glob patterns like *, ? and []. However, to avoid your shell accidentally
@@ -65,17 +65,17 @@ double quotes around each pattern.
--workspace--workspaceDocument all members in the workspace.
--all--allDeprecated alias for --workspace.
--exclude SPEC…--exclude SPEC…Exclude the specified packages. Must be used in conjunction with the
--workspace flag. This flag may be specified multiple times and supports
common Unix glob patterns like *, ? and []. However, to avoid your shell
@@ -98,29 +98,29 @@ the manifest settings. Using target selection options will ignore the `doc`
flag and will always document the given target.
--lib--libDocument the package’s library.
--bin name…--bin name…Document the specified binary. This flag may be specified multiple times and supports common Unix glob patterns.
--bins--binsDocument all binary targets.
--example name…--example name…Document the specified example. This flag may be specified multiple times and supports common Unix glob patterns.
--examples--examplesDocument all example targets.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
--target triple--target tripleDocument for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -178,20 +178,20 @@ target artifacts are placed in a separate directory. See the-r--release-r--releaseDocument optimized artifacts with the release profile.
See also the --profile option for choosing a specific profile by name.
--profile name--profile nameDocument with the given profile. See the reference for more details on profiles.
--timings=fmts--timings=fmtsOutput 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.
@@ -215,7 +215,7 @@ information about timing information.
### Output Options
--target-dir directory--target-dir directoryDirectory 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.
@@ -227,8 +227,8 @@ Defaults to target in the root of the workspace.
-v--verbose-v--verboseUse 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
@@ -236,15 +236,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -257,7 +257,7 @@ terminal.--message-format fmt--message-format fmtThe output format for diagnostic messages. Can be specified multiple times and consists of comma-separated values. Valid values:
human or <
### Manifest Options
--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--ignore-rust-version--ignore-rust-versionIgnore rust-version specification in packages.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -323,12 +323,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -346,7 +346,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -355,14 +355,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -374,13 +374,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
-Z unstable-options flag to enable (see
### Miscellaneous Options
-j N--jobs N-j N--jobs NNumber of parallel jobs to run. May also be specified with the
build.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
@@ -400,7 +400,7 @@ a string default is provided, it sets the value back to defaults.
Should not be 0.
--keep-going--keep-goingBuild 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,
diff --git a/src/doc/src/commands/cargo-fetch.md b/src/doc/src/commands/cargo-fetch.md
index ba8d72a34ce..b519199175a 100644
--- a/src/doc/src/commands/cargo-fetch.md
+++ b/src/doc/src/commands/cargo-fetch.md
@@ -28,7 +28,7 @@ you plan to use Cargo without a network with the `--offline` flag.
### Fetch options
--target triple--target tripleFetch for the specified target architecture. Flag may be specified multiple times. The default is all architectures. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -48,8 +48,8 @@ target artifacts are placed in a separate directory. See the ### Display Options-v--verbose-v--verboseUse 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
@@ -57,15 +57,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -82,13 +82,13 @@ terminal.--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -113,12 +113,12 @@ if there might be a newer version as indicated in the local copy of the index.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -136,7 +136,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -145,14 +145,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -164,13 +164,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--broken-code--broken-codeFix code even if it already has compiler errors. This is useful if cargo fix
fails to apply the changes. It will apply the changes and leave the broken
code in the working directory for you to inspect and manually fix.
--edition--editionApply changes that will update the code to the next edition. This will not
update the edition in the Cargo.toml manifest, which must be updated
manually after cargo fix --edition has finished.
--edition-idioms--edition-idiomsApply suggestions that will update code to the preferred style for the current edition.
--allow-no-vcs--allow-no-vcsFix code even if a VCS was not detected.
--allow-dirty--allow-dirtyFix code even if the working directory has changes (including staged changes).
--allow-staged--allow-stagedFix code even if the working directory has staged changes.
-p spec…--package spec…-p spec…--package spec…Fix only the specified packages. See cargo-pkgid(1) for the
SPEC format. This flag may be specified multiple times and supports common Unix
glob patterns like *, ? and []. However, to avoid your shell accidentally
@@ -129,17 +129,17 @@ double quotes around each pattern.
--workspace--workspaceFix all members in the workspace.
--all--allDeprecated alias for --workspace.
--exclude SPEC…--exclude SPEC…Exclude the specified packages. Must be used in conjunction with the
--workspace flag. This flag may be specified multiple times and supports
common Unix glob patterns like *, ? and []. However, to avoid your shell
@@ -166,40 +166,40 @@ use single quotes or double quotes around each glob pattern.
--lib--libFix the package’s library.
--bin name…--bin name…Fix the specified binary. This flag may be specified multiple times and supports common Unix glob patterns.
--bins--binsFix all binary targets.
--example name…--example name…Fix the specified example. This flag may be specified multiple times and supports common Unix glob patterns.
--examples--examplesFix all example targets.
--test name…--test name…Fix the specified integration test. This flag may be specified multiple times and supports common Unix glob patterns.
--tests--testsFix all targets that have the test = true manifest
flag set. By default this includes the library and binaries built as
unittests, and integration tests. Be aware that this will also build any
@@ -210,13 +210,13 @@ manifest settings for the target.
--bench name…--bench name…Fix the specified benchmark. This flag may be specified multiple times and supports common Unix glob patterns.
--benches--benchesFix all targets that have the bench = true
manifest flag set. By default this includes the library and binaries built
as benchmarks, and bench targets. Be aware that this will also build any
@@ -227,7 +227,7 @@ manifest settings for the target.
--all-targets--all-targetsFix all targets. This is equivalent to specifying --lib --bins --tests --benches --examples.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
--target triple--target tripleFix for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -285,14 +285,14 @@ target artifacts are placed in a separate directory. See the-r--release-r--releaseFix optimized artifacts with the release profile.
See also the --profile option for choosing a specific profile by name.
--profile name--profile nameFix with the given profile.
As a special case, specifying the test profile will also enable checking in
test mode which will enable checking tests and enable the test cfg option.
@@ -302,7 +302,7 @@ detail.
--timings=fmts--timings=fmtsOutput 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.
@@ -326,7 +326,7 @@ information about timing information.
### Output Options
--target-dir directory--target-dir directoryDirectory 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.
@@ -338,8 +338,8 @@ Defaults to target in the root of the workspace.
-v--verbose-v--verboseUse 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
@@ -347,15 +347,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -368,7 +368,7 @@ terminal.--message-format fmt--message-format fmtThe output format for diagnostic messages. Can be specified multiple times and consists of comma-separated values. Valid values:
human or <
### Manifest Options
--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--ignore-rust-version--ignore-rust-versionIgnore rust-version specification in packages.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -434,12 +434,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -457,7 +457,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -466,14 +466,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -485,13 +485,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
-Z unstable-options flag to enable (see
### Miscellaneous Options
-j N--jobs N-j N--jobs NNumber of parallel jobs to run. May also be specified with the
build.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
@@ -511,7 +511,7 @@ a string default is provided, it sets the value back to defaults.
Should not be 0.
--keep-going--keep-goingBuild 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,
diff --git a/src/doc/src/commands/cargo-generate-lockfile.md b/src/doc/src/commands/cargo-generate-lockfile.md
index 9b87b9363a0..bee7ef75963 100644
--- a/src/doc/src/commands/cargo-generate-lockfile.md
+++ b/src/doc/src/commands/cargo-generate-lockfile.md
@@ -22,8 +22,8 @@ lockfile and has more options for controlling update behavior.
### Display Options
-v--verbose-v--verboseUse 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
@@ -31,15 +31,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -56,18 +56,18 @@ terminal.--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--ignore-rust-version--ignore-rust-versionIgnore rust-version specification in packages.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -94,12 +94,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -117,7 +117,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -126,14 +126,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -145,13 +145,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
Fetch information about the specified package. The spec can be a package ID, see cargo-pkgid(1) for the SPEC
format.
If the specified package is part of the current workspace, information from the local Cargo.toml file will be displayed.
@@ -27,11 +27,11 @@ If the Cargo.lock file does not exist, it will be created. If no ve
selected based on the Minimum Supported Rust Version (MSRV).
--index index--index indexThe URL of the registry index to use.
--registry registry--registry registryName of the registry to use. Registry names are defined in Cargo config
files. If not specified, the default registry is used,
which is defined by the registry.default config key which defaults to
@@ -43,8 +43,8 @@ which is defined by the registry.default config key which defaults
### Display Options
-v--verbose-v--verboseUse 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
@@ -52,15 +52,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -77,7 +77,7 @@ terminal.--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -104,7 +104,7 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
+toolchain+toolchainIf 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).
@@ -123,14 +123,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -142,13 +142,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--bin--binCreate a package with a binary target (src/main.rs).
This is the default behavior.
--lib--libCreate a package with a library target (src/lib.rs).
--edition edition--edition editionSpecify the Rust edition to use. Default is 2024. Possible values: 2015, 2018, 2021, 2024
--name name--name nameSet the package name. Defaults to the directory name.
--vcs vcs--vcs vcsInitialize a new VCS repository for the given version control system (git,
hg, pijul, or fossil) or do not initialize any version control at all
(none). If not specified, defaults to git or the configuration value
@@ -59,7 +59,7 @@ hg, pijul, or fossil) or do not initialize any version control at all
--registry registry--registry registryThis sets the publish field in Cargo.toml to the given registry name
which will restrict publishing only to that registry.
Registry names are defined in Cargo config files. @@ -75,8 +75,8 @@ be restricted.
### Display Options-v--verbose-v--verboseUse 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
@@ -84,15 +84,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -110,7 +110,7 @@ terminal.+toolchain+toolchainIf 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).
@@ -119,14 +119,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -138,13 +138,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--vers version--version version--vers version--version versionSpecify a version to install. This may be a version
requirement, like ~1.2, to have Cargo
select the newest version from the given requirement. If the version does not
@@ -101,44 +101,44 @@ treated as a caret requirement like Cargo dependencies are.
--git url--git urlGit URL to install the specified crate from.
--branch branch--branch branchBranch to use when installing from git.
--tag tag--tag tagTag to use when installing from git.
--rev sha--rev shaSpecific commit to use when installing from git.
--path path--path pathFilesystem path to local crate to install from.
--list--listList all installed packages and their versions.
-n--dry-run-n--dry-run(unstable) Perform all checks without installing.
-f--force-f--forceForce overwriting existing crates or binaries. This can be used if a package
has installed a binary with the same name as another package. This is also
useful if something has changed on the system that you want to rebuild with,
@@ -146,7 +146,7 @@ such as a newer version of rustc.
--no-track--no-trackBy default, Cargo keeps track of the installed packages with a metadata file stored in the installation root directory. This flag tells Cargo not to use or create that file. With this flag, Cargo will refuse to overwrite any existing @@ -156,32 +156,32 @@ same time.
--bin name…--bin name…Install only the specified binary.
--bins--binsInstall all binaries. This is the default behavior.
--example name…--example name…Install only the specified example.
--examples--examplesInstall all examples.
--root dir--root dirDirectory to install packages into.
--registry registry--registry registryName of the registry to use. Registry names are defined in Cargo config
files. If not specified, the default registry is used,
which is defined by the registry.default config key which defaults to
@@ -189,7 +189,7 @@ which is defined by the registry.default config key which defaults
--index index--index indexThe URL of the registry index to use.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
--target triple--target tripleInstall for the specified target architecture. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -247,7 +247,7 @@ target artifacts are placed in a separate directory. See the--target-dir directory--target-dir directoryDirectory 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.
@@ -259,19 +259,19 @@ is specified.
--debug--debugBuild with the dev profile instead of the release profile.
See also the --profile option for choosing a specific profile by name.
--profile name--profile nameInstall with the given profile. See the reference for more details on profiles.
--timings=fmts--timings=fmtsOutput 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.
@@ -295,12 +295,12 @@ information about timing information.
### Manifest Options
--ignore-rust-version--ignore-rust-versionIgnore rust-version specification in packages.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -327,7 +327,7 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
-j N--jobs N-j N--jobs NNumber of parallel jobs to run. May also be specified with the
build.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
@@ -346,7 +346,7 @@ a string default is provided, it sets the value back to defaults.
Should not be 0.
--keep-going--keep-goingBuild 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,
@@ -361,8 +361,8 @@ builds, even if the one run first fails.
-v--verbose-v--verboseUse 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
@@ -370,15 +370,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -391,7 +391,7 @@ terminal.--message-format fmt--message-format fmtThe output format for diagnostic messages. Can be specified multiple times and consists of comma-separated values. Valid values:
human or <
+toolchain+toolchainIf 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).
@@ -430,14 +430,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -449,13 +449,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--workspace--workspaceLocate the Cargo.toml at the root of the workspace, as opposed to the current
workspace member.
--message-format fmt--message-format fmtThe representation in which to print the project location. Valid values:
json (default): JSON object with the path under the key “root”.-v--verbose-v--verboseUse 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
@@ -53,15 +53,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -78,7 +78,7 @@ terminal.--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
+toolchain+toolchainIf 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).
@@ -98,14 +98,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -117,13 +117,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--registry registry--registry registryName of the registry to use. Registry names are defined in Cargo config
files. If not specified, the default registry is used,
which is defined by the registry.default config key which defaults to
@@ -47,8 +47,8 @@ which is defined by the registry.default config key which defaults
### Display Options
-v--verbose-v--verboseUse 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
@@ -56,15 +56,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -82,7 +82,7 @@ terminal.+toolchain+toolchainIf 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).
@@ -91,14 +91,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -110,13 +110,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--registry registry--registry registryName of the registry to use. Registry names are defined in Cargo config
files. If not specified, the default registry is used,
which is defined by the registry.default config key which defaults to
@@ -46,8 +46,8 @@ which is defined by the registry.default config key which defaults
### Display Options
-v--verbose-v--verboseUse 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
@@ -55,15 +55,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -81,7 +81,7 @@ terminal.+toolchain+toolchainIf 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).
@@ -90,14 +90,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -109,13 +109,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--no-deps--no-depsOutput information only about the workspace members and don’t fetch dependencies.
--format-version version--format-version versionSpecify the version of the output format to use. Currently 1 is the only
possible value.
--filter-platform triple--filter-platform tripleThis filters the resolve output to only include dependencies for the
given target triple.
Without this flag, the resolve includes all targets.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
-v--verbose-v--verboseUse 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
@@ -416,15 +416,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -441,13 +441,13 @@ terminal.--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -474,12 +474,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -497,7 +497,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -506,14 +506,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -525,13 +525,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--bin--binCreate a package with a binary target (src/main.rs).
This is the default behavior.
--lib--libCreate a package with a library target (src/lib.rs).
--edition edition--edition editionSpecify the Rust edition to use. Default is 2024. Possible values: 2015, 2018, 2021, 2024
--name name--name nameSet the package name. Defaults to the directory name.
--vcs vcs--vcs vcsInitialize a new VCS repository for the given version control system (git,
hg, pijul, or fossil) or do not initialize any version control at all
(none). If not specified, defaults to git or the configuration value
@@ -54,7 +54,7 @@ hg, pijul, or fossil) or do not initialize any version control at all
--registry registry--registry registryThis sets the publish field in Cargo.toml to the given registry name
which will restrict publishing only to that registry.
Registry names are defined in Cargo config files. @@ -70,8 +70,8 @@ be restricted.
### Display Options-v--verbose-v--verboseUse 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
@@ -79,15 +79,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -105,7 +105,7 @@ terminal.+toolchain+toolchainIf 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).
@@ -114,14 +114,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -133,13 +133,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
-a--add login…-a--add login…Invite the given user or team as an owner.
-r--remove login…-r--remove login…Remove the given user or team as an owner.
-l--list-l--listList owners of a crate.
--token token--token tokenAPI token to use when authenticating. This overrides the token stored in the credentials file (which is created by cargo-login(1)).
Cargo config environment variables can be @@ -61,12 +61,12 @@ of the registry in all capital letters.
--index index--index indexThe URL of the registry index to use.
--registry registry--registry registryName of the registry to use. Registry names are defined in Cargo config
files. If not specified, the default registry is used,
which is defined by the registry.default config key which defaults to
@@ -79,8 +79,8 @@ which is defined by the registry.default config key which defaults
### Display Options
-v--verbose-v--verboseUse 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
@@ -88,15 +88,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -114,7 +114,7 @@ terminal.+toolchain+toolchainIf 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).
@@ -123,14 +123,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -142,13 +142,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
-l--list-l--listPrint files included in a package without making one.
--no-verify--no-verifyDon’t verify the contents by building them.
--no-metadata--no-metadataIgnore warnings about a lack of human-usable metadata (such as the description or the license).
--allow-dirty--allow-dirtyAllow working directories with uncommitted VCS changes to be packaged.
--exclude-lockfile--exclude-lockfileDon’t include the lock file when packaging.
This flag is not for general use.
Some tools may expect a lock file to be present (e.g. cargo install --locked).
@@ -106,12 +106,12 @@ Consider other options before using this.
--index index--index indexThe URL of the registry index to use.
--registry registry--registry registryName of the registry to package for; see cargo publish --help for more details
about configuration of registry names. The packages will not be published
to this registry, but if we are packaging multiple inter-dependent crates,
@@ -120,7 +120,7 @@ published to this registry.
--message-format fmt--message-format fmtSpecifies the output message format.
Currently, it only works with --list and affects the file listing format.
This is unstable and requires -Zunstable-options.
@@ -181,8 +181,8 @@ virtual workspace will include all workspace members (equivalent to passing
-p spec…--package spec…-p spec…--package spec…Package only the specified packages. See cargo-pkgid(1) for the
SPEC format. This flag may be specified multiple times and supports common Unix
glob patterns like *, ? and []. However, to avoid your shell accidentally
@@ -191,13 +191,13 @@ double quotes around each pattern.
--workspace--workspacePackage all members in the workspace.
--exclude SPEC…--exclude SPEC…Exclude the specified packages. Must be used in conjunction with the
--workspace flag. This flag may be specified multiple times and supports
common Unix glob patterns like *, ? and []. However, to avoid your shell
@@ -212,7 +212,7 @@ single quotes or double quotes around each pattern.
--target triple--target triplePackage for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -228,7 +228,7 @@ target artifacts are placed in a separate directory. See the--target-dir directory--target-dir directoryDirectory 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.
@@ -249,20 +249,20 @@ for more details.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -306,12 +306,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -329,8 +329,8 @@ requires the -Z unstable-options flag to enable (see
### Miscellaneous Options
-j N--jobs N-j N--jobs NNumber of parallel jobs to run. May also be specified with the
build.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
@@ -339,7 +339,7 @@ a string default is provided, it sets the value back to defaults.
Should not be 0.
--keep-going--keep-goingBuild 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,
@@ -354,8 +354,8 @@ builds, even if the one run first fails.
-v--verbose-v--verboseUse 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
@@ -363,15 +363,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -389,7 +389,7 @@ terminal.+toolchain+toolchainIf 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).
@@ -398,14 +398,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -417,13 +417,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
-p spec--package spec-p spec--package specGet the package ID for the given package instead of the current package.
-v--verbose-v--verboseUse 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
@@ -63,15 +63,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -89,13 +89,13 @@ terminal.--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -122,12 +122,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -146,7 +146,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -155,14 +155,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -174,13 +174,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--dry-run--dry-runPerform all checks without uploading.
--no-verify--no-verifyDon’t verify the contents by building them.
--allow-dirty--allow-dirtyAllow working directories with uncommitted VCS changes to be packaged.
--index index--index indexThe URL of the registry index to use.
--registry registry--registry registryName of the registry to publish to. Registry names are defined in Cargo
config files. If not specified, and there is a
package.publish field in
@@ -85,8 +85,8 @@ virtual workspace will include all workspace members (equivalent to passing
-p spec…--package spec…-p spec…--package spec…Publish only the specified packages. See cargo-pkgid(1) for the
SPEC format. This flag may be specified multiple times and supports common Unix
glob patterns like *, ? and []. However, to avoid your shell accidentally
@@ -95,17 +95,17 @@ double quotes around each pattern.
--workspace--workspacePublish all members in the workspace.
--all--allDeprecated alias for --workspace.
--exclude SPEC…--exclude SPEC…Exclude the specified packages. Must be used in conjunction with the
--workspace flag. This flag may be specified multiple times and supports
common Unix glob patterns like *, ? and []. However, to avoid your shell
@@ -120,7 +120,7 @@ single quotes or double quotes around each pattern.
--target triple--target triplePublish for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -136,7 +136,7 @@ target artifacts are placed in a separate directory. See the--target-dir directory--target-dir directoryDirectory 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.
@@ -157,20 +157,20 @@ for more details.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -214,12 +214,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -237,8 +237,8 @@ requires the -Z unstable-options flag to enable (see
### Miscellaneous Options
-j N--jobs N-j N--jobs NNumber of parallel jobs to run. May also be specified with the
build.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
@@ -247,7 +247,7 @@ a string default is provided, it sets the value back to defaults.
Should not be 0.
--keep-going--keep-goingBuild 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,
@@ -262,8 +262,8 @@ builds, even if the one run first fails.
-v--verbose-v--verboseUse 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
@@ -271,15 +271,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -297,7 +297,7 @@ terminal.+toolchain+toolchainIf 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).
@@ -306,14 +306,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -325,13 +325,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--dev--devRemove as a development dependency.
--build--buildRemove as a build dependency.
--target target--target targetRemove as a dependency to the given target platform.
To avoid unexpected shell expansions, you may use quotes around each target, e.g., --target 'cfg(unix)'.
--dry-run--dry-runDon’t actually write to the manifest.
-v--verbose-v--verboseUse 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
@@ -58,15 +58,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -83,13 +83,13 @@ terminal.--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -116,12 +116,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -139,8 +139,8 @@ requires the -Z unstable-options flag to enable (see
-p spec…--package spec…-p spec…--package spec…Package to remove from.
-Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -160,14 +160,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -179,13 +179,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
--id id--id idShow the report with the specified Cargo-generated id
-p spec…--package spec…-p spec…--package spec…Only display a report for the specified package
-p spec--package spec-p spec--package specThe package to run. See cargo-pkgid(1) for the SPEC format.
--bin name--bin nameRun the specified binary.
--example name--example nameRun the specified example.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
--target triple--target tripleRun for the specified target architecture. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -109,20 +109,20 @@ target artifacts are placed in a separate directory. See the-r--release-r--releaseRun optimized artifacts with the release profile.
See also the --profile option for choosing a specific profile by name.
--profile name--profile nameRun with the given profile. See the reference for more details on profiles.
--timings=fmts--timings=fmtsOutput 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.
@@ -146,7 +146,7 @@ information about timing information.
### Output Options
--target-dir directory--target-dir directoryDirectory 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.
@@ -159,8 +159,8 @@ Defaults to target in the root of the workspace.
-v--verbose-v--verboseUse 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
@@ -168,15 +168,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -189,7 +189,7 @@ terminal.--message-format fmt--message-format fmtThe output format for diagnostic messages. Can be specified multiple times and consists of comma-separated values. Valid values:
human or <
--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--ignore-rust-version--ignore-rust-versionIgnore rust-version specification in packages.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -257,12 +257,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -281,7 +281,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -290,14 +290,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -309,13 +309,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
-Z unstable-options flag to enable (see
### Miscellaneous Options
-j N--jobs N-j N--jobs NNumber of parallel jobs to run. May also be specified with the
build.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
@@ -335,7 +335,7 @@ a string default is provided, it sets the value back to defaults.
Should not be 0.
--keep-going--keep-goingBuild 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,
diff --git a/src/doc/src/commands/cargo-rustc.md b/src/doc/src/commands/cargo-rustc.md
index af33eb38ee4..4c9c73ccbac 100644
--- a/src/doc/src/commands/cargo-rustc.md
+++ b/src/doc/src/commands/cargo-rustc.md
@@ -37,8 +37,8 @@ flag can be used to choose a different package in a workspace.
-p spec--package spec-p spec--package specThe package to build. See cargo-pkgid(1) for the SPEC format.
--lib--libBuild the package’s library.
--bin name…--bin name…Build the specified binary. This flag may be specified multiple times and supports common Unix glob patterns.
--bins--binsBuild all binary targets.
--example name…--example name…Build the specified example. This flag may be specified multiple times and supports common Unix glob patterns.
--examples--examplesBuild all example targets.
--test name…--test name…Build the specified integration test. This flag may be specified multiple times and supports common Unix glob patterns.
--tests--testsBuild all targets that have the test = true manifest
flag set. By default this includes the library and binaries built as
unittests, and integration tests. Be aware that this will also build any
@@ -114,13 +114,13 @@ manifest settings for the target.
--bench name…--bench name…Build the specified benchmark. This flag may be specified multiple times and supports common Unix glob patterns.
--benches--benchesBuild all targets that have the bench = true
manifest flag set. By default this includes the library and binaries built
as benchmarks, and bench targets. Be aware that this will also build any
@@ -131,7 +131,7 @@ manifest settings for the target.
--all-targets--all-targetsBuild all targets. This is equivalent to specifying --lib --bins --tests --benches --examples.
-F features--features features-F features--features featuresSpace 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--all-featuresActivate all available features of all selected packages.
--no-default-features--no-default-featuresDo not activate the default feature of the selected packages.
--target triple--target tripleBuild for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>.
Possible values:
@@ -189,14 +189,14 @@ target artifacts are placed in a separate directory. See the-r--release-r--releaseBuild optimized artifacts with the release profile.
See also the --profile option for choosing a specific profile by name.
--profile name--profile nameBuild with the given profile.
The rustc subcommand will treat the following named profiles with special behaviors:
test profile.
--timings=fmts--timings=fmtsOutput 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.
@@ -232,7 +232,7 @@ information about timing information.
-
--crate-type crate-type--crate-type crate-typeBuild for the given crate type. This flag accepts a comma-separated list of
1 or more crate types, of which the allowed values are the same as crate-type
field in the manifest for configuring a Cargo target. See
@@ -249,7 +249,7 @@ the command-line argument value will override what is in the manifest.
--target-dir directory--target-dir directoryDirectory 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.
@@ -262,8 +262,8 @@ Defaults to target in the root of the workspace.
-v--verbose-v--verboseUse 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
@@ -271,15 +271,15 @@ May also be specified with the term.verbose
-q--quiet-q--quietDo not print cargo log messages.
May also be specified with the term.quiet
config value.
--color when--color whenControl when colored output is used. Valid values:
auto (default): Automatically detect if color support is available on the
@@ -292,7 +292,7 @@ terminal.--message-format fmt--message-format fmtThe output format for diagnostic messages. Can be specified multiple times and consists of comma-separated values. Valid values:
human or <
--manifest-path path--manifest-path pathPath to the Cargo.toml file. By default, Cargo searches for the
Cargo.toml file in the current directory or any parent directory.
--ignore-rust-version--ignore-rust-versionIgnore rust-version specification in packages.
--locked--lockedAsserts that the exact same dependencies and versions are used as when the
existing Cargo.lock file was originally generated. Cargo will exit with an
error when either of the following scenarios arises:
--offline--offlinePrevents 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 @@ -360,12 +360,12 @@ offline.
--frozen--frozenEquivalent to specifying both --locked and --offline.
--lockfile-path PATH--lockfile-path PATHChanges the path of the lockfile from the default (<workspace_root>/Cargo.lock) to PATH. PATH must end with
Cargo.lock (e.g. --lockfile-path /tmp/temporary-lockfile/Cargo.lock). Note that providing
--lockfile-path will ignore existing lockfile at the default path, and instead will
@@ -384,7 +384,7 @@ requires the -Z unstable-options flag to enable (see
+toolchain+toolchainIf 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).
@@ -393,14 +393,14 @@ for more information about how toolchain overrides work.
--config KEY=VALUE or PATH--config KEY=VALUE or PATHOverrides 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 for more information.
-C PATH-C PATHChanges 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
@@ -412,13 +412,13 @@ requires the -Z unstable-options flag to enable (see
-h--help-h--helpPrints help information.
-Z flag-Z flagUnstable (nightly-only) flags to Cargo. Run cargo -Z help for details.
-Z unstable-options flag to enable (see
### Miscellaneous Options
-j N--jobs N-j N--jobs NNumber of parallel jobs to run. May also be specified with the
build.jobs config value. Defaults to
the number of logical CPUs. If negative, it sets the maximum number of
@@ -438,7 +438,7 @@ a string default is provided, it sets the value back to defaults.
Should not be 0.
--keep-going--keep-goingBuild 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,
@@ -448,7 +448,7 @@ first), whereas cargo rustc -j1 --keep-going would definitely run b
builds, even if the one run first fails.
--future-incompat-report--future-incompat-reportDisplays a future-incompat report for any future-incompatible warnings produced during execution of this command
See cargo-report(1)
diff --git a/src/doc/src/commands/cargo-rustdoc.md b/src/doc/src/commands/cargo-rustdoc.md index ebb8b7b6358..d2b7e582cf8 100644 --- a/src/doc/src/commands/cargo-rustdoc.md +++ b/src/doc/src/commands/cargo-rustdoc.md @@ -34,7 +34,7 @@ or the `build.rustdocflags` [config value](../reference/config.html).