itsscb/cargo
1
0
Fork 0
mirror of https://github.com/rust-lang/cargo.git synced 2025-10-01 11:30:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

Auto merge of #13436 - ehuss:clarify-build-script-metadata, r=epage

Browse Source 
docs: Minor clarification of build script metadata.

This adds a minor clarification to the build script docs around links metadata. "As mentioned above in the output format" didn't really clue me in to what section it was talking about, or clearly tell me how to set the metadata.
This commit is contained in:
bors 2024-02-12 23:43:32 +00:00
commit 9d23d30943
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
src/doc/src/reference/build-scripts.md
View File

@ -376,14 +376,16 @@ In other words, it is forbidden to have two packages link to the same native
library. This helps prevent duplicate symbols between crates. Note, however, library. This helps prevent duplicate symbols between crates. Note, however,
that there are [conventions in place](#-sys-packages) to alleviate this. that there are [conventions in place](#-sys-packages) to alleviate this.
As mentioned above in the output format, each build script can generate an Build scripts can generate an arbitrary set of metadata in the form of
arbitrary set of metadata in the form of key-value pairs. This metadata is key-value pairs. This metadata is set with the `cargo::metadata=KEY=VALUE`
passed to the build scripts of **dependent** packages. For example, if the instruction.
package `bar` depends on `foo`, then if `foo` generates `key=value` as part of
its build script metadata, then the build script of `bar` will have the The metadata is passed to the build scripts of **dependent** packages. For
environment variables `DEP_FOO_KEY=value`. See the ["Using another `sys` example, if the package `bar` depends on `foo`, then if `foo` generates
crate"][using-another-sys] for an example of `key=value` as part of its build script metadata, then the build script of
how this can be used. `bar` will have the environment variables `DEP_FOO_KEY=value`. See the ["Using
another `sys` crate"][using-another-sys] for an example of how this can be
used.
Note that metadata is only passed to immediate dependents, not transitive Note that metadata is only passed to immediate dependents, not transitive
dependents. dependents.