Skip to content

Latest commit

 

History

History
137 lines (99 loc) · 6.87 KB

cargo-fetch.zh.md

File metadata and controls

137 lines (99 loc) · 6.87 KB
Raw

cargo-fetch(1)

NAME

cargo fetch（Cargo提取）-从网络中提取包的依赖项

SYNOPSIS

cargo fetch [options]

DESCRIPTION

如果Cargo.lock如果文件可用，此命令将确保所有git依赖项和/或注册表依赖项都已下载并在本地可用。随后的货运命令在发生故障后不会接触网络cargo fetch除非锁文件更改。

如果锁文件不可用，则此命令将在获取依赖项之前生成锁文件。

如果--target如果未指定，则将获取所有目标依赖项。

另见cargo-prefetch插件，它添加了一个命令来下载流行的箱子。如果您计划在没有网络的情况下使用Cargo--offline选项

OPTIONS

Fetch options

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

This may also be specified with the build.target config value.

Note that specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.

Display Options

-v
--verbose
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 term.verbose config value.
-q
--quiet
Do not print cargo log messages. May also be specified with the term.quiet config value.
--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.

Manifest Options

--manifest-path path
Path to the Cargo.toml file. By default, Cargo searches for the Cargo.toml file in the current directory or any parent directory.
--frozen
--locked
Either 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.

Common Options

+toolchain
If 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 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.

ENVIRONMENT

查看the reference有关Cargo读取的环境变量的详细信息。

EXIT STATUS

  • 0：Cargo成功。
  • 101：Cargo未能完成。

EXAMPLES

  1. 获取所有依赖项：

    提货

SEE ALSO

cargo(1), cargo-update(1), cargo-generate-lockfile(1)