mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-10-01 06:21:56 -09:00
docs/manual/adding-packages-python.adoc: clarify how _BUILD_OPTS work
PYTHON_FOO_BUILD_OPTS are passed to the build module call of the package build, this allows passing options to the python build *backend* by using the --config-setting= option. setup.py is no longer involved since even the setuptools backend now used the pep517 build method. The note about the options being passed to support/scripts/pyinstaller.py seems to be no longer accurate. Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu> [Arnout: also mention -C (suggested by James)] Signed-off-by: Arnout Vandecappelle <arnout@rnout.be>
This commit is contained in:
committed by
Arnout Vandecappelle
parent
70d5bac305
commit
b15cd1d8fe
@@ -128,10 +128,9 @@ therefore only use a few of them, or none.
|
|||||||
and +HOST_PKG_PYTHON_PEP517_ENV+ (for flit/pep517 host packages).
|
and +HOST_PKG_PYTHON_PEP517_ENV+ (for flit/pep517 host packages).
|
||||||
|
|
||||||
* +PYTHON_FOO_BUILD_OPTS+, to specify additional options to pass to
|
* +PYTHON_FOO_BUILD_OPTS+, to specify additional options to pass to
|
||||||
the Python +setup.py+ script during the build step, this generally
|
the Python +python -m build+ call. To pass additional options to the
|
||||||
only makes sense to use for setuptools based packages as flit/pep517
|
build backend use the +--config-setting=+ (+-C+) flag of the +build+
|
||||||
based packages do not pass these options to a +setup.py+ script but
|
module.
|
||||||
instead pass them to +support/scripts/pyinstaller.py+.
|
|
||||||
|
|
||||||
* +PYTHON_FOO_INSTALL_TARGET_OPTS+, +PYTHON_FOO_INSTALL_STAGING_OPTS+,
|
* +PYTHON_FOO_INSTALL_TARGET_OPTS+, +PYTHON_FOO_INSTALL_STAGING_OPTS+,
|
||||||
+HOST_PYTHON_FOO_INSTALL_OPTS+ to specify additional options to pass
|
+HOST_PYTHON_FOO_INSTALL_OPTS+ to specify additional options to pass
|
||||||
|
|||||||
Reference in New Issue
Block a user