13 Commits

Author	SHA1	Message	Date
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
David Hewitt	5119bad580	changelog: updates for 0.14.4	2021-08-29 08:07:44 +01:00
David Hewitt	bc1a983371	changelog: update for 0.14.3 release	2021-08-22 01:25:29 +01:00
David Hewitt	1873264b7d	release: 0.14.2	2021-08-09 07:58:31 +01:00
David Hewitt	3f8c4ad38e	release: 0.14.1	2021-07-04 16:49:36 +01:00
David Hewitt	adf6bdba8e	release: 0.14.0	2021-07-03 08:37:00 +01:00
David Hewitt	8fb4ce6fbc	pyo3-build-config: fix cross compilation	2021-06-26 14:19:03 +01:00
David Hewitt	825ec08681	pyo3-build-config: docs wip	2021-05-21 08:34:51 +01:00
David Hewitt	79c7149d52	pyo3-build-config: new crate to re-use build.rs across crates	2021-05-20 09:03:33 +01:00
David Hewitt	190eb72803	release: 0.13.2	2021-02-12 21:34:29 +00:00
David Hewitt	d2e87d95f3	release: 0.13.1	2021-01-10 12:20:10 +00:00
David Hewitt	26ca1f5bca	Release 0.13	2020-12-22 15:42:04 +00:00
David Hewitt	a689ab42c6	macros: rename crates for consistency	2020-12-20 06:39:28 +00:00

Renamed from pyo3-derive-backend/Cargo.toml (Browse further)