MAN page from OpenSuSE cargo-1.53.0-lp152.3.11.1.x86_64.rpm

CARGO\-FETCH

Section: Misc. Reference Manual Pages (1)
Index

NAME

cargo-fetch - Fetch dependencies of a package from the network

SYNOPSIS

cargo fetch [options]

DESCRIPTION

If a Cargo.lock file is available, this command will ensure that all of thegit dependencies and/or registry dependencies are downloaded and locallyavailable. Subsequent Cargo commands never touch the network after a cargo fetch unless the lock file changes.

If the lock file is not available, then this command will generate the lockfile before fetching the dependencies.

If --target is not specified, then all target dependencies are fetched.

See also the cargo-prefetch <https://crates.io/crates/cargo-prefetch>plugin which adds a command to download popular crates. This may be useful ifyou plan to use Cargo without a network with the --offline flag.

OPTIONS

Fetch options

--target triple

Fetch for the given architecture. The default is the hostarchitecture. The general format of the triple is<arch><sub>-<vendor>-<sys>-<abi>. Run rustc --print target-list for alist of supported targets.

This may also be specified with the build.targetconfig value <https://doc.rust-lang.org/cargo/reference/config.html>.

Note that specifying this flag makes Cargo run in a different mode where thetarget artifacts are placed in a separate directory. See thebuild cache <https://doc.rust-lang.org/cargo/guide/build-cache.html> documentation for more details.

Display Options

-v, --verbose

: Use verbose output. May be specified twice for "very verbose" output whichincludes extra output such as dependency warnings and build script output.May also be specified with the term.verboseconfig value <https://doc.rust-lang.org/cargo/reference/config.html>.

-q, --quiet

: 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 theterminal.

: *always: Always display colors.

: *never: Never display colors.

May also be specified with the term.colorconfig value <https://doc.rust-lang.org/cargo/reference/config.html>.

Manifest Options

--manifest-path path

: Path to the Cargo.toml file. By default, Cargo searches for theCargo.toml file in the current directory or any parent directory.

--frozen, --locked

: Either of these flags requires that the Cargo.lock file isup-to-date. If the lock file is missing, or it needs to be updated, Cargo willexit with an error. The --frozen flag also prevents Cargo fromattempting to access the network to determine if it is out-of-date.
These may be used in environments where you want to assert that theCargo.lock file is up-to-date (such as a CI build) or want to avoid networkaccess.

--offline

Prevents Cargo from accessing the network for any reason. Without thisflag, Cargo will stop with an error if it needs to access the network andthe network is not available. With this flag, Cargo will attempt toproceed without the network if possible.

Beware that this may result in different dependency resolution than onlinemode. Cargo will restrict itself to crates that are downloaded locally, evenif 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 goingoffline.

May also be specified with the net.offline config value <https://doc.rust-lang.org/cargo/reference/config.html>.

Common Options

+toolchain

: If Cargo has been installed with rustup, and the first argument to cargobegins with +, it will be interpreted as a rustup toolchain name (suchas +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