sharlatan pushed a commit to branch python-team-pyproject-build-system in repository guix.
commit d1f362d81c01544a1f16a0419075f025ff80df4f Author: Lars-Dominik Braun <[email protected]> AuthorDate: Fri Feb 16 09:44:50 2024 +0100 doc: Document new options for pyproject-build-system. * doc/guix.texi (Build Systems): Add documentation for changed #:configure-flags and new #:backend-path. Change-Id: Ic8be598ea52ae04230b1e61c329ee55ccbb5dd63 --- doc/guix.texi | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/guix.texi b/doc/guix.texi index 8f3b8ef6cd..3b53a1e763 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -9834,6 +9834,18 @@ The API is slightly different from @var{python-build-system}: @item @code{#:use-setuptools?} and @code{#:test-target} is removed. @item +@code{#:configure-flags} is changed. Instead of a list +this option must be a JSON object, whose interpretation +depends on the build backend. For instance the example from +@url{https://peps.python.org/pep-0517/#config-settings,PEP 517} +should be written as @code{'(@@ ("CC" "gcc") ("--global-option" +("--some-global-option")) ("--build-option" ("--build-option1" +"--build-option2")))} +@item +@code{#:backend-path} is added. It defaults to @code{#false}, but when +set to a list it will be appended to Python’s search path and overrides +the definition in @file{pyproject.toml}. +@item @code{#:build-backend} is added. It defaults to @code{#false} and will try to guess the appropriate backend based on @file{pyproject.toml}. @item
