cargo-vendor - Vendor all dependencies locally
cargo vendor [OPTIONS]
This cargo subcommand will vendor all crates.io and git
dependencies for a project into the specified directory at
<path>. After this command completes the vendor directory
specified by <path> will contain all remote sources from
dependencies specified. Additional manifests beyond the default one can be
specified with the -s option.
The cargo vendor command will also print out the
configuration necessary to use the vendored sources, which you will need to
add to .cargo/config.toml.
-s MANIFEST, --sync MANIFEST
Specify extra Cargo.toml manifests to workspaces
which should also be vendored and synced to the output.
Don’t delete the "vendor" directory when
vendoring, but rather keep all existing contents of the vendor directory
Instead of ignoring [source] configuration by
default in .cargo/config.toml read it and use it when downloading
crates from crates.io, for example
Normally versions are only added to disambiguate multiple
versions of the same package. This option causes all directories in the
"vendor" directory to be versioned, which makes it easier to track
the history of vendored packages over time, and can help with the performance
of re-vendoring when only a subset of the packages have changed.
Path to the Cargo.toml file. By default, Cargo
searches for the Cargo.toml file in the current directory or any parent
No output printed to stdout.
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
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
). See the
more information about how toolchain overrides work.
Prints help information.
Unstable (nightly-only) flags to Cargo. Run cargo -Z
help for details.
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.
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
Cargo failed to complete.
1.Vendor all dependencies into a local
2.Vendor all dependencies into a local
cargo vendor third-party/vendor
3.Vendor the current workspace as well as another to
cargo vendor -s ../path/to/Cargo.toml