Skip to content
Build library for invoking pkg-config for Rust
Rust
Branch: master
Clone or download
Latest commit 96e55cf Nov 2, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src Fixes #95 - multiple version numbers Oct 27, 2019
tests run cargo fmt Aug 27, 2019
.gitignore Changed PKG_CONFIG env variable name Jan 23, 2018
.travis.yml Fix .travis.yml syntax Sep 4, 2019
CHANGELOG.md Release 0.3.17 Nov 2, 2019
Cargo.toml Release 0.3.17 Nov 2, 2019
LICENSE-APACHE Initial commit Nov 1, 2014
LICENSE-MIT Initial commit Nov 1, 2014
README.md Document that we require at least Rust 1.30 now Sep 4, 2019

README.md

pkg-config-rs

Build Status Rust

Documentation

A simple library meant to be used as a build dependency with Cargo packages in order to use the system pkg-config tool (if available) to determine where a library is located.

You can use this crate directly to probe for specific libraries, or use metadeps to declare all your pkg-config dependencies in Cargo.toml.

This library requires Rust 1.30+.

Example

Find the system library named foo, with minimum version 1.2.3:

extern crate pkg_config;

fn main() {
    pkg_config::Config::new().atleast_version("1.2.3").probe("foo").unwrap();
}

Find the system library named foo, with no version requirement (not recommended):

extern crate pkg_config;

fn main() {
    pkg_config::probe_library("foo").unwrap();
}

External configuration via target-scoped environment variables

In cross-compilation context, it is useful to manage separately PKG_CONFIG_PATH and a few other variables for the host and the target platform.

The supported variables are: PKG_CONFIG_PATH, PKG_CONFIG_LIBDIR, and PKG_CONFIG_SYSROOT_DIR.

Each of these variables can also be supplied with certain prefixes and suffixes, in the following prioritized order:

  1. <var>_<target> - for example, PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  2. <var>_<target_with_underscores> - for example, PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  3. <build-kind>_<var> - for example, HOST_PKG_CONFIG_PATH or TARGET_PKG_CONFIG_PATH
  4. <var> - a plain PKG_CONFIG_PATH

Also note that PKG_CONFIG_ALLOW_CROSS must always be set in cross-compilation context.

License

This project is licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in pkg-config-rs by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

You can’t perform that action at this time.