Gregory Szorc 1e951d5d8b pyo3-build-config: add a crate feature to control build script ... I have a use case in PyOxidizer where I want to use the pyo3-build-config crate as a library crate so I can access the `InterpreterConfig` struct so I can read/write config files without reinventing the wheel. This is doable before this commit. But it requires that the build environment have a Python interpreter. This is undesirable for library usage. This commit introduces a cargo feature flag to control whether the build script does anything. The feature flag must be present for the build script to resolve a config. The feature flag is enabled by default for backwards compatibility. The pyo3 and pyo3-macros-backend crates use this feature by default, for backwards compatibility and because it is the reasonable default. This is probably room to conditionalize some APIs and other behavior based on this feature flag. But we stop short of doing that for the time being.		2021-09-01 19:44:54 -07:00
..
src	Merge pull request #1847 from davidhewitt/test-parse-sysconfigdata	2021-09-01 08:50:29 +01:00
Cargo.toml	pyo3-build-config: add a crate feature to control build script	2021-09-01 19:44:54 -07:00
LICENSE	pyo3-build-config: new crate to re-use build.rs across crates	2021-05-20 09:03:33 +01:00
build.rs	pyo3-build-config: add a crate feature to control build script	2021-09-01 19:44:54 -07:00