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.
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.
Build and install a Rust binary.
Create a new Cargo package.
Search packages in crates.io.
Remove a Rust binary.
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.
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>.
Binaries installed by cargo-install(1) will be located here. If using rustup, executables distributed with Rust are also located here.
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.
cargo build --release
cargo test --target i686-unknown-linux-gnu
cargo new foobar
mkdir foo && cd foo cargo init .
cargo help clean