|
NAMEcargo - The Rust package managerSYNOPSIScargo [options] command [args]cargo [options] --version cargo [options] --list cargo [options] --help cargo [options] --explain code DESCRIPTIONThis program is a package manager and build tool for the Rust language, available at <https://rust-lang.org>.COMMANDSBuild Commandscargo-bench(1)Execute benchmarks of a package. cargo-build(1)
cargo-check(1)
cargo-clean(1)
cargo-doc(1)
cargo-fetch(1)
cargo-fix(1)
cargo-run(1)
cargo-rustc(1)
cargo-rustdoc(1)
cargo-test(1)
Manifest Commandscargo-generate-lockfile(1)Generate Cargo.lock for a project. cargo-locate-project(1)
cargo-metadata(1)
cargo-pkgid(1)
cargo-tree(1)
cargo-update(1)
cargo-vendor(1)
cargo-verify-project(1)
Package Commandscargo-init(1)Create a new Cargo package in an existing directory. cargo-install(1)
cargo-new(1)
cargo-search(1)
cargo-uninstall(1)
Publishing Commandscargo-login(1)Save an API token from the registry locally. cargo-owner(1)
cargo-package(1)
cargo-publish(1)
cargo-yank(1)
General Commandscargo-help(1)Display help information about Cargo. cargo-version(1)
OPTIONSSpecial Options-V, --versionPrint version info and exit. If used with
--verbose, prints extra information.
--list List all installed Cargo subcommands. If used with
--verbose, prints extra information.
--explain code Run rustc --explain CODE which will print out a
detailed explanation of an error message (for example, E0004).
Display Options-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
config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
-q, --quiet Do not print cargo log messages. May also be specified
with the term.quiet config value
<https://doc.rust-lang.org/cargo/reference/config.html>.
--color when Control when colored output is used. Valid values:
•auto (default): Automatically detect if
color support is available on the terminal.
•always: Always display colors.
•never: Never display colors.
May also be specified with the term.color config value <https://doc.rust-lang.org/cargo/reference/config.html>. Manifest Options--frozen, --lockedEither of these flags requires that the Cargo.lock
file is up-to-date. If the lock file is missing, or it needs to be updated,
Cargo will exit with an error. The --frozen flag also prevents Cargo
from attempting to access the network to determine if it is out-of-date.
These may be used in environments where you want to assert that the Cargo.lock file is up-to-date (such as a CI build) or want to avoid network access. --offline Prevents Cargo from accessing the network for any reason.
Without this flag, Cargo will stop with an error if it needs to access the
network and the network is not available. With this flag, Cargo will attempt
to proceed without the network if possible.
Beware that this may result in different dependency resolution than online mode. Cargo will restrict itself to crates that are downloaded locally, even if there might be a newer version as indicated in the local copy of the index. See the cargo-fetch(1) command to download dependencies before going offline. May also be specified with the net.offline config value <https://doc.rust-lang.org/cargo/reference/config.html>. Common Options+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). See the
rustup documentation
<https://rust-lang.github.io/rustup/overrides.html> for more information
about how toolchain overrides work.
-h, --help Prints help information.
-Z flag Unstable (nightly-only) flags to Cargo. Run cargo -Z
help for details.
ENVIRONMENTSee the reference <https://doc.rust-lang.org/cargo/reference/environment-variables.html> for details on environment variables that Cargo reads.EXIT STATUS•0: Cargo succeeded.
•101: Cargo failed to complete.
FILES~/.cargo/Default location for Cargo's "home" directory where it stores various files. The location can be changed with the CARGO_HOME environment variable. $CARGO_HOME/bin/
$CARGO_HOME/config.toml
.cargo/config.toml
$CARGO_HOME/credentials.toml
$CARGO_HOME/registry/
$CARGO_HOME/git/
Please note that the internal structure of the $CARGO_HOME directory is not stable yet and may be subject to change. EXAMPLES 1.Build a local package and all of its dependencies:
cargo build 2.Build a package with optimizations:
cargo build --release 3.Run tests for a cross-compiled target:
cargo test --target i686-unknown-linux-gnu 4.Create a new package that builds an executable:
cargo new foobar 5.Create a package in the current directory:
mkdir foo && cd foo cargo init . 6.Learn about a command's options and usage:
cargo help clean BUGSSee <https://github.com/rust-lang/cargo/issues> for issues.SEE ALSOrustc(1), rustdoc(1) Visit the GSP FreeBSD Man Page Interface. |