mirror/buildroot
1
0
Fork 0
mirror of https://gitlab.com/buildroot.org/buildroot.git synced 2026-09-19 16:40:46 -09:00
Code Issues Packages Projects Releases Wiki Activity

package/pkg-python.mk: add hatch setup type

Browse Source 
As we have many python packages using the hatch(hatchling) build
system we should add a setup type for it so that we don't have to
manually specify the host-python-hatchling dependency.

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
This commit is contained in:
James Hilliard
2024-10-08 16:27:24 -06:00
committed by Thomas Petazzoni
parent 7e739d49b2
commit 1459c0a6f0
4 changed files with 41 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/manual/adding-packages-directory.adoc
View File

@@ -429,9 +429,9 @@ different way, using different infrastructures:
and xref:cmake-package-reference[reference].
* *Makefiles for Python modules*: We have a dedicated infrastructure
for Python modules that use the +flit+, +pep517+, +setuptools+,
+setuptools-rust+ or +maturin+ mechanisms. We cover them through a
xref:python-package-tutorial[tutorial] and a
for Python modules that use the +flit+, +hatch+, +pep517+,
+setuptools+, +setuptools-rust+ or +maturin+ mechanisms. We cover
them through a xref:python-package-tutorial[tutorial] and a
xref:python-package-reference[reference].
* *Makefiles for Lua modules*: We have a dedicated infrastructure for

14
docs/manual/adding-packages-python.adoc
View File

@@ -51,9 +51,9 @@ On line 13, we declare our dependencies, so that they are built
before the build process of our package starts.
On line 14, we declare the specific Python build system being used. In
this case the +setuptools+ Python build system is used. The five
supported ones are +flit+, +pep517+, +setuptools+, +setuptools-rust+
and +maturin+.
this case the +setuptools+ Python build system is used. The six
supported ones are +flit+, +hatch+, +pep517+, +setuptools+,
+setuptools-rust+ and +maturin+.
Finally, on line 16, we invoke the +python-package+ macro that
generates all the Makefile rules that actually allow the package to be
@@ -96,10 +96,10 @@ Note that:
One variable specific to the Python infrastructure is mandatory:
* +PYTHON_FOO_SETUP_TYPE+, to define which Python build system is used
by the package. The five supported values are +flit+, +pep517+ and
+setuptools+, +setuptools-rust+ and +maturin+. If you don't know
which one is used in your package, look at the +setup.py+ or
+pyproject.toml+ file in your package source code, and see whether
by the package. The five supported values are +flit+, +hatch+,
+pep517+ and +setuptools+, +setuptools-rust+ and +maturin+. If you
don't know which one is used in your package, look at the +setup.py+
or +pyproject.toml+ file in your package source code, and see whether
it imports things from the +flit+ module or the +setuptools+
module. If the package is using a +pyproject.toml+ file without any
build-system requires and with a local in-tree backend-path one