1CARGO-GENERATE-LOCKFILE(1)                          CARGO-GENERATE-LOCKFILE(1)
2
3
4

NAME

6       cargo-generate-lockfile - Generate the lockfile for a package
7

SYNOPSIS

9       cargo generate-lockfile [OPTIONS]
10

DESCRIPTION

12       This command will create the Cargo.lock lockfile for the current
13       package or workspace. If the lockfile already exists, it will be
14       rebuilt if there are any manifest changes or dependency updates.
15
16       See also cargo-update(1) which is also capable of creating a Cargo.lock
17       lockfile and has more options for controlling update behavior.
18

OPTIONS

20   Display Options
21       -v, --verbose
22           Use verbose output. May be specified twice for "very verbose"
23           output which includes extra output such as dependency warnings and
24           build script output. May also be specified with the term.verbose
25           config value
26           <https://doc.rust-lang.org/cargo/reference/config.html>.
27
28       -q, --quiet
29           No output printed to stdout.
30
31       --color WHEN
32           Control when colored output is used. Valid values:
33
34           ·   auto (default): Automatically detect if color support is
35               available on the terminal.
36
37           ·   always: Always display colors.
38
39           ·   never: Never display colors.
40
41           May also be specified with the term.color config value
42           <https://doc.rust-lang.org/cargo/reference/config.html>.
43
44   Manifest Options
45       --manifest-path PATH
46           Path to the Cargo.toml file. By default, Cargo searches in the
47           current directory or any parent directory for the Cargo.toml file.
48
49       --frozen, --locked
50           Either of these flags requires that the Cargo.lock file is
51           up-to-date. If the lock file is missing, or it needs to be updated,
52           Cargo will exit with an error. The --frozen flag also prevents
53           Cargo from attempting to access the network to determine if it is
54           out-of-date.
55
56           These may be used in environments where you want to assert that the
57           Cargo.lock file is up-to-date (such as a CI build) or want to avoid
58           network access.
59
60   Common Options
61       -h, --help
62           Prints help information.
63
64       -Z FLAG...
65           Unstable (nightly-only) flags to Cargo. Run cargo -Z help for
66           details.
67

ENVIRONMENT

69       See the reference
70       <https://doc.rust-lang.org/cargo/reference/environment-variables.html>
71       for details on environment variables that Cargo reads.
72

EXIT STATUS

74       0
75           Cargo succeeded.
76
77       101
78           Cargo failed to complete.
79

EXAMPLES

81        1. Create or update the lockfile for the current package or workspace:
82
83               cargo generate-lockfile
84

SEE ALSO

86       cargo(1), cargo-update(1)
87
88
89
90                                  2018-12-20        CARGO-GENERATE-LOCKFILE(1)
Impressum