]> git.proxmox.com Git - cargo.git/commit - tests/testsuite/cargo_add/add_basic/mod.rs
Auto merge of #10600 - tmfink:doc-build-script-link-order, r=ehuss
authorbors <bors@rust-lang.org>
Wed, 25 May 2022 00:50:02 +0000 (00:50 +0000)
committerbors <bors@rust-lang.org>
Wed, 25 May 2022 00:50:02 +0000 (00:50 +0000)
commit39ad1039d9e3e1746177bf5d134af4c164f95528
treeac530e42174d0180560762915ea0b1e9d4019023
parente7c8ba7753bbfc2015754422d6d65bb59c30ea56
parent43ce1e7a98c3bfb9cb1314c3a248e481d4a05234
Auto merge of #10600 - tmfink:doc-build-script-link-order, r=ehuss

doc: discuss build script instruction order

### What does this PR try to resolve?

It is currently not documented that the order of build script `cargo:` instructions may be relevant to linking.

This has caused issues such as: https://github.com/rust-lang/rust/issues/96328

### How should we test and review this PR?

Build/view documentation.

### Additional information

- Cargo maintainers should fact check my wording.
- We may need to discuss if this should also be documented for `rustc`
- Maintainers should ensure that this change does not prevent a change in what is currently unspecified behavior. Perhaps `cargo` will want to rearrange link arguments itself to resolve issues in the future?
src/doc/src/reference/build-scripts.md
tests/testsuite/build_script.rs