rust
/
cargo
mirror of https://github.com/rust-lang/cargo
0
0
Fork 0
Code Issues Releases Wiki Activity

docs(ref): Provide path for people to finding why shared Cargo.lock matters

This commit is contained in:
Ed Page 2022-09-13 14:08:01 -05:00 committed by Weihang Lo
parent 7997f1e9cf
commit a1c48c56fe
No known key found for this signature in database
GPG Key ID: D7DBF189825E82E7
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/doc/src/reference/workspaces.md
View File

@ -6,7 +6,7 @@ members*, that are managed together.
The key points of workspaces are:
* Common commands can run across all workspace members, like `cargo check --workspace`.
* All packages share a common `Cargo.lock` file which resides in the
* All packages share a common [`Cargo.lock`] file which resides in the
*workspace root*.
* All packages share a common [output directory], which defaults to a
directory named `target` in the *workspace root*.
@ -240,6 +240,7 @@ to the data in `workspace.metadata` if data is missing from `package.metadata`,
if that makes sense for the tool in question.
[package]: manifest.md#the-package-section
[`Cargo.lock`]: ../guide/cargo-toml-vs-cargo-lock.md
[package-metadata]: manifest.md#the-metadata-table
[output directory]: ../guide/build-cache.md
[patch]: overriding-dependencies.md#the-patch-section