|CARGO(1)||General Commands Manual||CARGO(1)|
cargo [options] --version
cargo [options] --list
cargo [options] --help
cargo [options] --explain code
Execute benchmarks of a package.
Compile a package.
Check a local package and all of its dependencies for errors.
Remove artifacts that Cargo has generated in the past.
Build a package's documentation.
Fetch dependencies of a package from the network.
Automatically fix lint warnings reported by rustc.
Run a binary or example of the local package.
Compile a package, and pass extra options to the compiler.
Build a package's documentation, using specified custom flags.
Execute unit and integration tests of a package.
Generate Cargo.lock for a project.
Print a JSON representation of a Cargo.toml file's location.
Output the resolved dependencies of a package in machine-readable format.
Print a fully qualified package specification.
Display a tree visualization of a dependency graph.
Update dependencies as recorded in the local lock file.
Vendor all dependencies locally.
Check correctness of crate manifest.
Create a new Cargo package in an existing directory.
Build and install a Rust binary.
Create a new Cargo package.
Search packages in crates.io.
Remove a Rust binary.
Save an API token from the registry locally.
Manage the owners of a crate on the registry.
Assemble the local package into a distributable tarball.
Upload a package to the registry.
Remove a pushed crate from the index.
Display help information about Cargo.
Show version information.
May also be specified with the term.color config value https://doc.rust-lang.org/cargo/reference/config.html.
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.
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.
Default location for Cargo's "home" directory where it stores various files. The location can be changed with the CARGO_HOME environment variable.
The global configuration file. See the reference https://doc.rust-lang.org/cargo/reference/config.html for more information about configuration files.
Cargo automatically searches for a file named .cargo/config.toml in the current directory, and all parent directories. These configuration files will be merged with the global configuration file.
Private authentication information for logging in to a registry.
This directory contains cached downloads of the registry index and any downloaded dependencies.
This directory contains cached downloads of git dependencies.
Please note that the internal structure of the $CARGO_HOME directory is not stable yet and may be subject to change.
cargo build --release
cargo test --target i686-unknown-linux-gnu
cargo new foobar
mkdir foo && cd foo cargo init .
cargo help clean