system-deps 1.3.2

Discover and configure system dependencies from declarative dependencies in Cargo.toml
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

# system-deps [![](https://img.shields.io/crates/v/system-deps.svg)](https://crates.io/crates/system-deps) [![](https://docs.rs/system-deps/badge.svg)](https://docs.rs/system-deps)

`system-deps` lets you write system dependencies in `Cargo.toml` metadata,
rather than programmatically in `build.rs`. This makes those dependencies
declarative, so other tools can read them as well.

For now only `pkg-config` dependencies are supported but we are planning to
[expand it](https://github.com/gdesmott/system-deps/issues/3) at some point.

Users can override dependency flags using environment variables if needed.
`system-deps` also allows `-sys` crates to optionally internally build and
static link the required system library.

`system-deps` has been started as a fork of the
[metadeps](https://github.com/joshtriplett/metadeps) project.

## Documentation

See the [crate documentation](https://docs.rs/system-deps/).

## Usage

In your `Cargo.toml`:

```toml
[build-dependencies]
system-deps = "1.3"
```

Then, to declare a dependency on `testlib >= 1.2`
add the following section:

```toml
[package.metadata.system-deps]
testlib = "1.2"
```

Finally, in your `build.rs`, add:

```rust
fn main() {
    system_deps::Config::new().probe().unwrap();
}
```

See the [crate documentation](https://docs.rs/system-deps/) for more advanced features.