docs/manual/adding-packages-python.txt

10 [[python-package-tutorial]]
12 ==== +python-package+ tutorial
14 First, let's see how to write a +.mk+ file for a Python package,
33 16: $(eval $(python-package))
36 On line 7, we declare the version of the package.
42 On line 10 and 11, we give licensing details about the package (its
47 +setup.py+ script when it is configuring the package.
50 before the build process of our package starts.
56 Finally, on line 16, we invoke the +python-package+ macro that
57 generates all the Makefile rules that actually allow the package to be
60 [[python-package-reference]]
62 ==== +python-package+ reference
78 The main macro of the Python package infrastructure is
79 +python-package+. It is similar to the +generic-package+ macro. It is
81 +host-python-package+ macro.
84 by defining a number of variables before calling the +python-package+
85 or +host-python-package+ macros.
87 All the package metadata information variables that exist in the
88 xref:generic-package-reference[generic package infrastructure] also
97    +PYTHON_FOO_DEPENDENCIES+ variable of a package, since these basic
99    package infrastructure.
108   by the package. The two supported values are +distutils+ and
109   +setuptools+. If you don't know which one is used in your package,
110   look at the +setup.py+ file in your package source code, and see
115 optionally be defined, depending on the package's needs. Many of them
120   package that contains the main +setup.py+ file. This is useful,
155   will ensure the right host python package is available and will
168   infrastructure is used, if the package +.mk+ file defines its own
175 ==== Generating a +python-package+ from a PyPI repository
177 If the Python package for which you would like to create a Buildroot
178 package is available on PyPI, you may want to use the +scanpypi+ tool
184 +scanpypi+ requires Python's +setuptools+ package to be installed on
190 utils/scanpypi foo bar -o package
193 This will generate packages +python-foo+ and +python-bar+ in the package
196 Find the +external python modules+ menu and insert your package inside.
200 package for any mistakes as there are things that cannot be guessed by
204 need to manually add the package to the +package/Config.in+ file.
206 If your Buildroot package is not in the official Buildroot tree but in
214 +other_package_directory+ instead of +package+.
222 [[python-package-cffi-backend]]
224 ==== +python-package+ CFFI backend
232 Such a package should:
236 +select BR2_PACKAGE_PYTHON_CFFI+ to the package +Config.in+.
259 $(eval $(python-package))