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

docs/manual/adding-packages-python.txt: fix outdated Python 3 explanation

Browse Source 
Python packages should no longer depend on BR2_PACKAGE_PYTHON in their
config file, unless they are only compatible with Python 2.

Signed-off-by: Raphaël Mélotte <raphael.melotte@essensium.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
(cherry picked from commit b5c553ba59)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
Raphaël Mélotte
2019-09-09 13:58:07 +02:00
committed by Peter Korsgaard
parent a1b83af9b6
commit 549f7be31d
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/manual/adding-packages-python.txt
View File

@@ -67,9 +67,13 @@ Python build system, but are not Python modules, can freely choose
their name (existing examples in Buildroot are +scons+ and their name (existing examples in Buildroot are +scons+ and
+supervisor+). +supervisor+).
In their +Config.in+ file, they should depend on +BR2_PACKAGE_PYTHON+ Packages that are only compatible with one version of Python (as in:
so that when Buildroot will enable Python 3 usage for modules, we will Python 2 or Python 3) should depend on that version explicitely in
be able to enable Python modules progressively on Python 3. their +Config.in+ file (+BR2_PACKAGE_PYTHON+ for Python 2,
+BR2_PACKAGE_PYTHON3+ for Python 3). Packages that are compatible
with both versions should not explicitely depend on them in their
+Config.in+ file, since that condition is already expressed for the
whole "External python modules" menu.
The main macro of the Python package infrastructure is The main macro of the Python package infrastructure is
+python-package+. It is similar to the +generic-package+ macro. It is +python-package+. It is similar to the +generic-package+ macro. It is