Auto merge of #14312 - weihanglo:doc, r=epage

docs: clarify `target.'cfg(...)'`  doesnt respect cfg from build script
This commit is contained in:
bors 2024-09-30 20:53:38 +00:00
commit dc041a0599

View File

@ -1173,9 +1173,9 @@ rustflags = ["…", "…"]
```
`cfg` values come from those built-in to the compiler (run `rustc --print=cfg`
to view), values set by [build scripts], and extra `--cfg` flags passed to
`rustc` (such as those defined in `RUSTFLAGS`). Do not try to match on
`debug_assertions` or Cargo features like `feature="foo"`.
to view) and extra `--cfg` flags passed to `rustc` (such as those defined in
`RUSTFLAGS`). Do not try to match on `debug_assertions`, `test`, Cargo features
like `feature="foo"`, or values set by [build scripts].
If using a target spec JSON file, the [`<triple>`] value is the filename stem.
For example `--target foo/bar.json` would match `[target.bar]`.