Lines Matching +full:cross +full:- +full:compilation

1 # pkg-config-rs
3 …tus](https://github.com/rust-lang/pkg-config-rs/actions/workflows/ci.yml/badge.svg)](https://githu…
4 …[Rust](https://img.shields.io/badge/rust-1.30%2B-blue.svg?maxAge=3600)](https://github.com/rust-la…
6 [Documentation](https://docs.rs/pkg-config)
9 order to use the system `pkg-config` tool (if available) to determine where a
13 [system-deps](https://github.com/gdesmott/system-deps) to declare all your
14 `pkg-config` dependencies in `Cargo.toml`.
41 # External configuration via target-scoped environment variables
43 In cross-compilation context, it is useful to manage separately `PKG_CONFIG_PATH`
51 1. `<var>_<target>` - for example, `PKG_CONFIG_PATH_x86_64-unknown-linux-gnu`
52 2. `<var>_<target_with_underscores>` - for example, `PKG_CONFIG_PATH_x86_64_unknown_linux_gnu`
53 3. `<build-kind>_<var>` - for example, `HOST_PKG_CONFIG_PATH` or `TARGET_PKG_CONFIG_PATH`
54 4. `<var>` - a plain `PKG_CONFIG_PATH`
56 This crate will allow `pkg-config` to be used in cross-compilation
58 to bypass the compatibility check, but please note that enabling use of `pkg-config` in
59 cross-compilation without appropriate sysroot and search paths set is likely to break builds.
62 around for lack of cross-compilation support in `pkg-config`.
68  * Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or
69    https://www.apache.org/licenses/LICENSE-2.0)
70  * MIT license ([LICENSE-MIT](LICENSE-MIT) or
78 for inclusion in pkg-config-rs by you, as defined in the Apache-2.0 license, shall be