Lines Matching full:packages

4 === Infrastructure for Python packages
6 This infrastructure applies to Python packages that use the standard
64 As a policy, packages that merely provide Python modules should all be
65 named +python-<something>+ in Buildroot. Other packages that use the
70 Packages that are only compatible with one version of Python (as in:
73 +BR2_PACKAGE_PYTHON3+ for Python 3).  Packages that are compatible
80 also possible to create Python host packages with the
102    +PYTHON_FOO_DEPENDENCIES+ for setuptools-based packages, since it's
116 are only useful in very specific cases, typical packages will
129   (for distutils target packages), +HOST_PKG_PYTHON_DISTUTILS_ENV+
130   (for distutils host packages), +PKG_PYTHON_SETUPTOOLS_ENV+ (for
131   setuptools target packages) and +HOST_PKG_PYTHON_SETUPTOOLS_ENV+
132   (for setuptools host packages).
136   packages, the +PKG_PYTHON_DISTUTILS_BUILD_OPTS+ options are already
146   packages), +HOST_PKG_PYTHON_DISTUTILS_INSTALL_OPTS+ (for host
147   distutils packages), +PKG_PYTHON_SETUPTOOLS_INSTALL_TARGET_OPTS+ or
149   packages) and +HOST_PKG_PYTHON_SETUPTOOLS_INSTALL_OPTS+ (for host
150   setuptools packages).
154   packages. The two supported value are +python2+ and +python3+. It
160 install the packages are already defined, and they generally work well
161 for most Python-based packages. However, when required, it is still
181 You can find the list of existing PyPI packages
193 This will generate packages +python-foo+ and +python-bar+ in the package
213 This will generate packages +python-foo+ and +python-bar+ in the
228 declarations written in C. Python packages relying on this backend can