Skip to content

Latest commit

 

History

History
126 lines (89 loc) · 5.79 KB

cargo-verify-project.zh.md

File metadata and controls

126 lines (89 loc) · 5.79 KB
Raw

cargo-verify-project(1)

NAME

Cargo验证项目-检查箱子舱单的正确性

SYNOPSIS

cargo verify-project [options]

DESCRIPTION

此命令将解析本地清单并检查其有效性。它会发出一个JSON对象，并给出结果。成功的验证将显示：

{"success":"true"}

无效的工作区将显示：

{"invalid":"human-readable error message"}

OPTIONS

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：工作区正常。
  • 1：工作区无效。

EXAMPLES

  1. 检查当前工作区是否存在错误：

    Cargo验证项目

SEE ALSO

cargo(1), cargo-package(1)