Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add some hints to the docs for cfg() targets #6990

Merged
merged 3 commits into from
May 28, 2019
Merged

Add some hints to the docs for cfg() targets #6990

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
03294f8
Add some hints to the docs for `cfg()` targets
notriddle May 27, 2019
f2663ba
Update specifying-dependencies.md
notriddle May 28, 2019
69f9adb
Link cfg, remove old note, fix link.
ehuss May 28, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 14 additions & 3 deletions src/doc/src/reference/specifying-dependencies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -440,7 +440,8 @@ Cargo how to find local unpublished crates.


Platform-specific dependencies take the same format, but are listed under a
`target` section. Normally Rust-like `#[cfg]` syntax will be used to define
`target` section. Normally Rust-like [`#[cfg]`
syntax](../reference/conditional-compilation.html) will be used to define
these sections:

```toml
Expand All @@ -458,8 +459,18 @@ native = { path = "native/x86_64" }
```

Like with Rust, the syntax here supports the `not`, `any`, and `all` operators
to combine various cfg name/value pairs. Note that the `cfg` syntax has only
been available since Cargo 0.9.0 (Rust 1.8.0).
to combine various cfg name/value pairs.

If you want to know which cfg targets are available on your platform, run
`rustc --print=cfg` from the command line. If you want to know which `cfg`
targets are available for another platform, such as 64-bit Windows,
run `rustc --print=cfg --target=x86_64-pc-windows-msvc`.

Unlike in your Rust source code,
you cannot use `[target.'cfg(feature = "my_crate")'.dependencies]` to add
dependencies based on optional crate features.
Use [the `[features]` section](reference/manifest.html#the-features-section)
instead.

In addition to `#[cfg]` syntax, Cargo also supports listing out the full target
the dependencies would apply to:
Expand Down