1CARGO-VENDOR(1) CARGO-VENDOR(1)
2
6 cargo-vendor - Vendor all dependencies locally
7
9 cargo vendor [OPTIONS] [PATH]
10
12 This cargo subcommand will vendor all crates.io and git dependencies
13 for a project into the specified directory at <path>. After this
14 command completes the vendor directory specified by <path> will contain
15 all remote sources from dependencies specified. Additional manifests
16 beyond the default one can be specified with the -s option.
17 The cargo vendor command will also print out the configuration
19 necessary to use the vendored sources, which you will need to add to
20 .cargo/config.
21
23 Owner Options
24 -s MANIFEST, --sync MANIFEST
25 Specify extra Cargo.toml manifests to workspaces which should also
26 be vendored and synced to the output.
27 --no-delete
29 Don’t delete the "vendor" directory when vendoring, but rather keep
30 all existing contents of the vendor directory
31 --respect-source-config
33 Instead of ignoring [source] configuration by default in
34 .cargo/config read it and use it when downloading crates from
35 crates.io, for example
36 Manifest Options
38 --manifest-path PATH
39 Path to the Cargo.toml file. By default, Cargo searches in the
40 current directory or any parent directory for the Cargo.toml file.
41 Display Options
43 -v, --verbose
44 Use verbose output. May be specified twice for "very verbose"
45 output which includes extra output such as dependency warnings and
46 build script output. May also be specified with the term.verbose
47 config value
48 <https://doc.rust-lang.org/cargo/reference/config.html>.
49 -q, --quiet
51 No output printed to stdout.
52 --color WHEN
54 Control when colored output is used. Valid values:
55 · auto (default): Automatically detect if color support is
57 available on the terminal.
58 · always: Always display colors.
60 · never: Never display colors.
62 May also be specified with the term.color config value
64 <https://doc.rust-lang.org/cargo/reference/config.html>.
65 Common Options
67 -h, --help
68 Prints help information.
69 -Z FLAG...
71 Unstable (nightly-only) flags to Cargo. Run cargo -Z help for
72 details.
73 --frozen, --locked
75 Either of these flags requires that the Cargo.lock file is
76 up-to-date. If the lock file is missing, or it needs to be updated,
77 Cargo will exit with an error. The --frozen flag also prevents
78 Cargo from attempting to access the network to determine if it is
79 out-of-date.
80 These may be used in environments where you want to assert that the
82 Cargo.lock file is up-to-date (such as a CI build) or want to avoid
83 network access.
84 --offline
86 Prevents Cargo from accessing the network for any reason. Without
87 this flag, Cargo will stop with an error if it needs to access the
88 network and the network is not available. With this flag, Cargo
89 will attempt to proceed without the network if possible.
90 Beware that this may result in different dependency resolution than
92 online mode. Cargo will restrict itself to crates that are
93 downloaded locally, even if there might be a newer version as
94 indicated in the local copy of the index. See the cargo-fetch(1)
95 command to download dependencies before going offline.
96 May also be specified with the net.offline config value
98 <https://doc.rust-lang.org/cargo/reference/config.html>.
99
101 See the reference
102 <https://doc.rust-lang.org/cargo/reference/environment-variables.html>
103 for details on environment variables that Cargo reads.
104
106 0
107 Cargo succeeded.
108 101
110 Cargo failed to complete.
111
113 1. Vendor all dependencies into a local "vendor" folder
114 cargo vendor
116 2. Vendor all dependencies into a local "third-party/vendor" folder
118 cargo vendor third-party/vendor
120 3. Vendor the current workspace as well as another to "vendor"
122 cargo vendor -s ../path/to/Cargo.toml
124
126 cargo(1)
127 2019-09-05 CARGO-VENDOR(1)