cargo-fetch - Fetch dependencies of a package from the network
cargo fetch [OPTIONS]
Cargo.lock file is available, this command will ensure that all of the
git dependencies and/or registry dependencies are downloaded and locally
available. Subsequent Cargo commands never touch the network after a
fetch unless the lock file changes.
If the lock file is not available, then this command will generate the lock file before fetching the dependencies.
--target is not specified, then all target dependencies are fetched.
- --target TRIPLE
Fetch for the given architecture. The default is the host architecture. The general format of the triple is
rustc --print target-listfor a list of supported targets.
This may also be specified with the
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
No output printed to stdout.
- --color WHEN
Control when colored output is used. Valid values:
auto(default): Automatically detect if color support is available on the terminal.
always: Always display colors.
never: Never display colors.
May also be specified with the
- --manifest-path PATH
Path to the
Cargo.tomlfile. By default, Cargo searches in the current directory or any parent directory for the
Either of these flags requires that the
Cargo.lockfile is up-to-date. If the lock file is missing, or it needs to be updated, Cargo will exit with an error. The
--frozenflag 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.lockfile is up-to-date (such as a CI build) or want to avoid network access.
Prints help information.
- -Z FLAG…
Unstable (nightly-only) flags to Cargo. Run
cargo -Z helpfor details.
See the reference for details on environment variables that Cargo reads.
Cargo failed to complete.
Fetch all dependencies: