LILiK
/
openwrt-packages-dist
5
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
25923 Commits
1 Branch
46 MiB
Tree: 80ef61729b
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '80ef61729b'
${ noResults }
openwrt-packages-dist/lang/python/python3/Makefile

396 lines
13 KiB
Raw Normal View History

python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: upgrade to version 3.5.1 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
9 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
​
​
​
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python,python3: export mk files outside of python package dirs Since `lang/python` is it's own folder of Python packages (for both Python 2 & 3), and these build rules are needed in a lot of packages [especially Python packages], putting them here makes sense architecturally, to be shared. This also helps get rid of the `include_mk` construct which relies on OpenWrt core to provide, and seems like a broken design idea that has persisted for a while. Reason is: it requires that Python 2/3 be built to provide these mk files for other Python packages, which seems like a bad idea. Long-term, there could be an issue where some other feeds would require these mk files [e.g. telephony] for some Python packages. We'll see how we handle this a bit later. For now we limit this to this feed. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
7 years ago
python: upgrade to version 3.4.1 Some notes: - Python 3 (at least version 3.4) is pretty cross-compiler-friendly, so a lot of patches were thrown away. - Arguments below were moved to ./files/config.site file, and disabled ac_cv_have_chflags=no \ ac_cv_have_lchflags=no \ ac_cv_py_format_size_t=no \ ac_cv_have_long_long_format=yes \ ac_cv_buggy_getaddrinfo=no \ - --without-ensurepip added, because the build wants to ensure that it works; that's a good idea, but for now, it requires special setup, and we can do that later - --without-pymalloc added, becase in Python 3, modules are suffixed with m; e.g. so some paths are python3.4m instead of python3.4 all this is detailed here: http://legacy.python.org/dev/peps/pep-3149/ Maybe it will be a good idea to re-add this back Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
rename package name to python3
10 years ago
python3: enable bluetooth support by default Bluetooth support requires bluez-libs present, but they are only required for the build, and don't seem to be needed to be present on the target. There isn't any linking required to libbluetooth. It's only the bluetooth.h header that is required for building BT support into Python. For testing, this snippet was used from `Lib/test/test_socket.py` (inside cpython): ``` def _have_socket_bluetooth(): """Check whether AF_BLUETOOTH sockets are supported on this host.""" try: # RFCOMM is supported by all platforms with bluetooth support. Windows # does not support omitting the protocol. s = socket.socket(socket.AF_BLUETOOTH, socket.SOCK_STREAM, socket.BTPROTO_RFCOMM) except (AttributeError, OSError): return False else: s.close() return True ``` Fixes: https://github.com/openwrt/packages/issues/16544 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
3 years ago
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: Download source archive via https Signed-off-by: Florian Fieber <florian@florianfieber.de>
10 years ago
python3: bump version to 3.9.7 Refreshed patches. And apply hack for line-endings in pep517 (from pip). Hack comment: # FIXME: [1] get rid of this asap; 'patch' doesn't like Windows endings, and this file is full of them... # I actually tried this in a number of ways and the only way to fix this is to implement # a poor-man's dos2unix using sed. # The issue is with the pip package; it seems that it throws in some Windows line-endings # and 'patch' won't handle them. So, we do a "dos2unix" and then patch. # We can get rid of this once this is solved upstream and in pip: # https://github.com/pypa/pep517/pull/130 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
3 years ago
​
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Update to version 3.7.4 - Update setuptools to 40.8.0 - Update pip to 19.0.3 - Refreshed patches - Removed 4 patches (2 of them was included in 3.7.3 and other two are included in this release) Makefile python3: - Move PKG_MAINTAINER above PKG_LICENSE Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
6 years ago
python3: refresh LICENSE information Changed PKG_LICENSE to reflect spdx license tag, and PKG_LICENSE_FILES to include all lincense-related files applicable to the parts of the code we are actually using to build and/or distributing. The Windows-only files, and the python-bundled Tools we're not using have been left out. Signed-off-by: Eneas U de Queiroz <cote2004-github@yahoo.com>
6 years ago
​
python: Add PKG_CPE_ID for proper CVE tracking Signed-off-by: Rosen Penev <rosenp@gmail.com>
6 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: sync makefiles with python package Technically, this just updates build details. No functionality change to package itself. So, no need to increase PKG_RELEASE on this change. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python,python3: export mk files outside of python package dirs Since `lang/python` is it's own folder of Python packages (for both Python 2 & 3), and these build rules are needed in a lot of packages [especially Python packages], putting them here makes sense architecturally, to be shared. This also helps get rid of the `include_mk` construct which relies on OpenWrt core to provide, and seems like a broken design idea that has persisted for a while. Reason is: it requires that Python 2/3 be built to provide these mk files for other Python packages, which seems like a bad idea. Long-term, there could be an issue where some other feeds would require these mk files [e.g. telephony] for some Python packages. We'll see how we handle this a bit later. For now we limit this to this feed. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
7 years ago
python3: sync makefiles with python package Technically, this just updates build details. No functionality change to package itself. So, no need to increase PKG_RELEASE on this change. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
​
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python,python3: export mk files outside of python package dirs Since `lang/python` is it's own folder of Python packages (for both Python 2 & 3), and these build rules are needed in a lot of packages [especially Python packages], putting them here makes sense architecturally, to be shared. This also helps get rid of the `include_mk` construct which relies on OpenWrt core to provide, and seems like a broken design idea that has persisted for a while. Reason is: it requires that Python 2/3 be built to provide these mk files for other Python packages, which seems like a bad idea. Long-term, there could be an issue where some other feeds would require these mk files [e.g. telephony] for some Python packages. We'll see how we handle this a bit later. For now we limit this to this feed. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
7 years ago
python3: split `python3-version.mk` from `python3-package.mk` And move \`python3-package.mk\` include, same as in python package. This is mostly to have consistency/similarity between python & python3 packages. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python,python3: apply PKG_FIXUP:=autoreconf Should hopefully provide more consistent results across distros. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
7 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
​
​
​
python,python3: build bluetooth support if bluez-libs selected This should hopefully fix the Python3 build on buildbot. For a while I assumed it may be a build-bot issue, but then looking through the packages repo [and finding the bluez package] it looks like, if you try to build all packages, Python3 detects the bluetooth headers installed by bluez. It looks like Python's bluetooth support was somewhat broken ; it was not detecting the <bluetooth/bluetooth.h> header, so a backport from Python3 to Python fixed that. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
7 years ago
python,python3: split python[3]-pkg-resources from setuptools This package is required by other packages to run some binaries via `load_entry_point`. So, this splits this package away from setuptools. setuptools is pretty big, akd pkg-resources is also big, but not as big. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
5 years ago
python3: enable bluetooth support by default Bluetooth support requires bluez-libs present, but they are only required for the build, and don't seem to be needed to be present on the target. There isn't any linking required to libbluetooth. It's only the bluetooth.h header that is required for building BT support into Python. For testing, this snippet was used from `Lib/test/test_socket.py` (inside cpython): ``` def _have_socket_bluetooth(): """Check whether AF_BLUETOOTH sockets are supported on this host.""" try: # RFCOMM is supported by all platforms with bluetooth support. Windows # does not support omitting the protocol. s = socket.socket(socket.AF_BLUETOOTH, socket.SOCK_STREAM, socket.BTPROTO_RFCOMM) except (AttributeError, OSError): return False else: s.close() return True ``` Fixes: https://github.com/openwrt/packages/issues/16544 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
3 years ago
python,python3: add dependency on CONFIG_PACKAGE_ symbols for setuptools & pip If you build python/python3 and later decide to build python(3)-setuptools and/or python(3)-pip, the build won't re-run without adding `CONFIG_PACKAGE_python(3)-setuptools` and `CONFIG_PACKAGE_python(3)-pip`. Seems to resolve issue: https://github.com/openwrt/packages/issues/4529 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python3: enable bluetooth support by default Bluetooth support requires bluez-libs present, but they are only required for the build, and don't seem to be needed to be present on the target. There isn't any linking required to libbluetooth. It's only the bluetooth.h header that is required for building BT support into Python. For testing, this snippet was used from `Lib/test/test_socket.py` (inside cpython): ``` def _have_socket_bluetooth(): """Check whether AF_BLUETOOTH sockets are supported on this host.""" try: # RFCOMM is supported by all platforms with bluetooth support. Windows # does not support omitting the protocol. s = socket.socket(socket.AF_BLUETOOTH, socket.SOCK_STREAM, socket.BTPROTO_RFCOMM) except (AttributeError, OSError): return False else: s.close() return True ``` Fixes: https://github.com/openwrt/packages/issues/16544 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
3 years ago
expat: don't build host libs tools/expat is actually what's used by the various packages that supposedly depend on expat/host. Signed-off-by: Rosen Penev <rosenp@gmail.com>
3 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
rename package name to python3
10 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python3: Download source archive via https Signed-off-by: Florian Fieber <florian@florianfieber.de>
10 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
rename package name to python3
10 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
​
​
​
​
python3: introduce libpython3 with ABI_VERSION flag Related to discussion: https://github.com/openwrt/packages/pull/14060 Every once in a while a version bump will occur that requires an ABI change. Example: Python 3.8 to 3.9. When this happens some Python packages would need to be rebuilt. In setups where everything gets rebuilt, this isn't a problem. It's usually a bigger problem when needing to upgrade something via opkg. To accommodate for this, we add a libpython with it's own ABI_VERSION flag. If this ABI_VERSION changes, then this should propagate forward. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 years ago
​
​
​
​
​
​
​
​
​
​
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
rename package name to python3
10 years ago
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python3: introduce libpython3 with ABI_VERSION flag Related to discussion: https://github.com/openwrt/packages/pull/14060 Every once in a while a version bump will occur that requires an ABI change. Example: Python 3.8 to 3.9. When this happens some Python packages would need to be rebuilt. In setups where everything gets rebuilt, this isn't a problem. It's usually a bigger problem when needing to upgrade something via opkg. To accommodate for this, we add a libpython with it's own ABI_VERSION flag. If this ABI_VERSION changes, then this should propagate forward. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
​
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python3: enable bluetooth support by default Bluetooth support requires bluez-libs present, but they are only required for the build, and don't seem to be needed to be present on the target. There isn't any linking required to libbluetooth. It's only the bluetooth.h header that is required for building BT support into Python. For testing, this snippet was used from `Lib/test/test_socket.py` (inside cpython): ``` def _have_socket_bluetooth(): """Check whether AF_BLUETOOTH sockets are supported on this host.""" try: # RFCOMM is supported by all platforms with bluetooth support. Windows # does not support omitting the protocol. s = socket.socket(socket.AF_BLUETOOTH, socket.SOCK_STREAM, socket.BTPROTO_RFCOMM) except (AttributeError, OSError): return False else: s.close() return True ``` Fixes: https://github.com/openwrt/packages/issues/16544 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
3 years ago
python,python3: define config option for bluetooth support It was reported via https://github.com/openwrt/packages/pull/5122#issuecomment-347395472 that if bluez-libs is selected as an installable package, then the error below will show up: ``` * satisfy_dependencies_for: Cannot satisfy the following dependencies for python-light: * bluez-libs * * opkg_install_cmd: Cannot install package python-light. ``` This looks like a limitation in the design of package deps, and maybe a misuse of conditional deps (i.e. PACKAGE_bluez-libs:bluez-libs). So, to fix this, an idea we're adding an extra symbol that enfoces installation of bluez-libs if selected. We also need to add a way to disable bluetooth build if PYTHON(3)_BLUETOOTH_SUPPORT is de-selected. Otherwise, bluetooth is installed and the socket module is broken due to linker errors. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
7 years ago
​
​
​
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
​
​
​
​
​
​
python3: upgrade to version 3.5.0 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
9 years ago
python3: sync makefiles with python package Technically, this just updates build details. No functionality change to package itself. So, no need to increase PKG_RELEASE on this change. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: sync makefiles with python package Technically, this just updates build details. No functionality change to package itself. So, no need to increase PKG_RELEASE on this change. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
​
​
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
​
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python,python3: do not package binary files to base packages Thanks to fix 200a5a2eec896b2d34f1114d14df66d810c1f4bd all base packages now contain all binaries that are generated as part of python installation. That causes collision between those packages with package managers that consider this such as Turris updater-ng. This is also just wrong. Those binaries were not included and should not be after mentioned fix as well. This just adds empty install definition. The idea is to override the default one that is otherwise used. Signed-off-by: Karel Kočí <karel.koci@nic.cz>
6 years ago
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: sync makefiles with python package Technically, this just updates build details. No functionality change to package itself. So, no need to increase PKG_RELEASE on this change. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
rename package name to python3
10 years ago
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: Fix host build tool names recorded in target files Python will record the values of CC, CXX, AR, and READELF (and other configure options) used during compilation. pip will use these programs when asked to compile extension modules on the target device. * If ccache is used during build, CC and CXX will be ccache_cc and ccache_cxx, respectively, which are not available on-device (#11912). * If an external toolchain is used during build, the values of these variables will contain the external toolchain prefix, which may not be available on target. * If the normal toolchain is used during build, AR and READELF will contain the toolchain prefix, but the names of ar and readelf on-device do not contain the prefix; they are named "ar" and "readelf". This changes the values of these variables in Python's files to match the names available on-device, and without any toolchain prefix. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
​
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: bump to version 3.8 This required a bit work to get working, compared to other versions. So, some things have changed a bit more significantly. Some highlights: * there is no longer a pgen executable, seems this is now part of libpython; let's see what this means for us in the future * blake2 hash (from OpenSSL) detection needs some fixing; will upstream added patch 002-fix-blake2-detection.patch * removed all bpo patches; those should be fixed in upstream * some needed to be manually re-applied as stuff changed: - 001-enable-zlib.patch - file changed - 004-do-not-write-bytes-codes.patch - file changed - 015-abort-on-failed-modules.patch - variable was renamed cross_compiling -> CROSS_COMPILING * 017_lib2to3_fix_pyc_search.patch - the code changed, it does not seem to have the original problem with respect to file-extension, as there does not seem to be any special extension logic anymore there * 006-remove-multi-arch-and-local-paths.patch - dropped patch; I can't remember the full-details of this issue; it was something with Debian/Ubuntu's multi-arch stuff; it was probably added maybe due to some overzealous (on my part) thingy caused by some weird reports, that I could never solve; let's have this patch dropped and see * make package/python3/refresh to reduce fuzz for the rest Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
5 years ago
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
python3: fix compilation Because of e52d0487e88c3c8c57e1310d1a02b18eae0d142e , these flags no longer get passed. Add them back to fix compilation. Signed-off-by: Rosen Penev <rosenp@gmail.com>
4 years ago
​
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Enable compile-time optimizations This adds the --enable-optimizations configure option (for profile-guided optimization) for both host and target Python, and the --with-lto configure option (for link-time optimization) for target Python (for non-MIPS platforms). Currently, compiling Python with LTO leads to link errors on mips and mipsel. (Compiling with LTO appears to succeed on mips64 but there is only one mips64 target available for convenient testing.) This also cleans up the host and target configure options: * Sort options/variables - Alphabetically - Flags/options before child-process environment variables - Group options by type (enable/disable/with/without) - Static options/variables before conditional ones * Remove the prefix/dir options, as they are the same as the defaults set by the build system * Remove --with-threads, as it is no longer a valid option (threads are always enabled) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: upgrade to version 3.6.0 Python 3.6 comes with some new cross-compilation logic that generates filenames/paths with arch, abiflags and mach included (in filename & path). Problem is that the generated paths/filenames are not consistent across archs (noticed on x86_64 & ar71xx), so patch `016-adjust-config-paths.patch` was added to mitigate this (by removing extra stuff in paths). Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python3: Enable compile-time optimizations This adds the --enable-optimizations configure option (for profile-guided optimization) for both host and target Python, and the --with-lto configure option (for link-time optimization) for target Python (for non-MIPS platforms). Currently, compiling Python with LTO leads to link errors on mips and mipsel. (Compiling with LTO appears to succeed on mips64 but there is only one mips64 target available for convenient testing.) This also cleans up the host and target configure options: * Sort options/variables - Alphabetically - Flags/options before child-process environment variables - Group options by type (enable/disable/with/without) - Static options/variables before conditional ones * Remove the prefix/dir options, as they are the same as the defaults set by the build system * Remove --with-threads, as it is no longer a valid option (threads are always enabled) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python3: Enable compile-time optimizations This adds the --enable-optimizations configure option (for profile-guided optimization) for both host and target Python, and the --with-lto configure option (for link-time optimization) for target Python (for non-MIPS platforms). Currently, compiling Python with LTO leads to link errors on mips and mipsel. (Compiling with LTO appears to succeed on mips64 but there is only one mips64 target available for convenient testing.) This also cleans up the host and target configure options: * Sort options/variables - Alphabetically - Flags/options before child-process environment variables - Group options by type (enable/disable/with/without) - Static options/variables before conditional ones * Remove the prefix/dir options, as they are the same as the defaults set by the build system * Remove --with-threads, as it is no longer a valid option (threads are always enabled) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: enable bluetooth support by default Bluetooth support requires bluez-libs present, but they are only required for the build, and don't seem to be needed to be present on the target. There isn't any linking required to libbluetooth. It's only the bluetooth.h header that is required for building BT support into Python. For testing, this snippet was used from `Lib/test/test_socket.py` (inside cpython): ``` def _have_socket_bluetooth(): """Check whether AF_BLUETOOTH sockets are supported on this host.""" try: # RFCOMM is supported by all platforms with bluetooth support. Windows # does not support omitting the protocol. s = socket.socket(socket.AF_BLUETOOTH, socket.SOCK_STREAM, socket.BTPROTO_RFCOMM) except (AttributeError, OSError): return False else: s.close() return True ``` Fixes: https://github.com/openwrt/packages/issues/16544 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
3 years ago
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python,python3: split python[3]-pkg-resources from setuptools This package is required by other packages to run some binaries via `load_entry_point`. So, this splits this package away from setuptools. setuptools is pretty big, akd pkg-resources is also big, but not as big. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
5 years ago
​
​
​
​
​
​
​
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python-setuptools,python-pip: Set pip cache dir, disable version check This adds --cache-dir and --disable-pip-version-check options for host pip, when "installing" target setuptools and pip. This also changes the pip command to use $(HOST_PYTHON[3]_PIP) from python[3]-host.mk. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
​
​
​
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python-setuptools,python-pip: Change prefix to /usr This changes the --prefix option, passed to host pip when "installing" target setuptools and pip, to /usr, in case the prefix is recorded in the packages. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
​
python3: Update to 3.8.4, refresh/rework patches, backport patches This version includes fixes for: * CVE-2020-14422: Hash collisions in IPv4Interface and IPv6Interface * CVE-2020-15523: Python uses invalid DLL path after calling Py_SetPath on Windows This version also includes support for OpenSSL 1.1.x builds that use 'no-deprecated' and '--api=1.1.0'[1], and so this removes the previous OpenSSL-related patches. This also backports fixes for security issues, including: * CVE-2019-20907: Infinite loop in the tarfile module This also updates the setuptools and pip packages to 47.1.0 and 20.1.1, respectively. [1]: https://github.com/python/cpython/pull/20566 Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python-setuptools,python-pip: Change prefix to /usr This changes the --prefix option, passed to host pip when "installing" target setuptools and pip, to /usr, in case the prefix is recorded in the packages. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python3: do a simple ls on pip & setuptools if not selected for build I seem to forget to check/select setuptools and pip (that come bundled with Python). This change will do a simple 'ls' on the 2 wheel files, so that the build fails even if just building Python. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 years ago
​
​
​
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
​
​
​
python-setuptools,python-pip: Set pip cache dir, disable version check This adds --cache-dir and --disable-pip-version-check options for host pip, when "installing" target setuptools and pip. This also changes the pip command to use $(HOST_PYTHON[3]_PIP) from python[3]-host.mk. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
​
​
​
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python-setuptools,python-pip: Change prefix to /usr This changes the --prefix option, passed to host pip when "installing" target setuptools and pip, to /usr, in case the prefix is recorded in the packages. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
​
python3: bump version to 3.9.5 Refreshed Python patches. Updated pip & setuptools version. For pip, patch '001-pep517-pyc-fix.patch' was reworked. Also, the current version of the bundled pip (21.1.1) no longer supports Python2, so the 'py2.py3' suffix gets replaced with just py3. For setuptools, there is no longer a script/module: https://github.com/pypa/setuptools/pull/2544 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 years ago
python3: bump version to 3.9.7 Refreshed patches. And apply hack for line-endings in pep517 (from pip). Hack comment: # FIXME: [1] get rid of this asap; 'patch' doesn't like Windows endings, and this file is full of them... # I actually tried this in a number of ways and the only way to fix this is to implement # a poor-man's dos2unix using sed. # The issue is with the pip package; it seems that it throws in some Windows line-endings # and 'patch' won't handle them. So, we do a "dos2unix" and then patch. # We can get rid of this once this is solved upstream and in pip: # https://github.com/pypa/pep517/pull/130 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
3 years ago
​
​
​
​
​
​
​
python-setuptools,python-pip: Change prefix to /usr This changes the --prefix option, passed to host pip when "installing" target setuptools and pip, to /usr, in case the prefix is recorded in the packages. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python3: do a simple ls on pip & setuptools if not selected for build I seem to forget to check/select setuptools and pip (that come bundled with Python). This change will do a simple 'ls' on the 2 wheel files, so that the build fails even if just building Python. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 years ago
​
​
​
pip,setuptools: move as part of python,python3 build Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
​
​
​
​
​
​
​
​
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python,python3: Use only target package data for Build/InstallDev This changes Build/InstallDev for both Python 2 and 3 to only copy files from target Python, not from host Python, since InstallDev files are used for target packages to link to other target packages. In particular, usr/lib/python{2.7,3.7}/_sysconfigdata.py holds system configuration data generated at build time, and is different for target Python and host Python. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python,python3: Move python-config to $(STAGING_DIR)/host Build/InstallDev is passed a second argument, a path where host binaries should be placed (ultimately $(STAGING_DIR)/host). This change moves python[3]-config to that directory. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Use default _PYTHON_HOST_PLATFORM This lets the Python build process set _PYTHON_HOST_PLATFORM instead of forcing an explicit value. Also: * Save the target _PYTHON_HOST_PLATFORM value during Build/InstallDev for use when building target Python packages (in python3-package.mk). * Use the (mostly) default PYTHON_FOR_BUILD value, instead patch configure to remove the platform triplet from the sysconfigdata file name. * Remove the "CROSS_COMPILE=yes" make variable (there is no indication that this variable is necessary). * Force host pip to build packages from source instead of downloading binary wheels. Previously, host pip can download universal (platform-independent) wheels but not platform-specific wheels, because of the custom _PYTHON_HOST_PLATFORM value. (Packages that do not have universal wheels would be compiled from source.) With a correct _PYTHON_HOST_PLATFORM, host pip can install platform-specific wheels as well. However, the pre-built shared object (.so) files in these wheels will have the host's platform triplet in their file names. When target Python packages are built (using the target's _PYTHON_HOST_PLATFORM), Python will not use these shared object files. By forcing host pip to build packages from source, the built shared object files will not have the platform triplet in their file names. (Host Python has been patched to remove the platform triplet from file names.) This allows these packages to be used when building target Python packages. (The net effect of this complete change is that platform-dependent packages will continue to be compiled from source, while platform-independent packages will now also be compiled from source.) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
​
​
python3: install pkgconfig to staging Some programs that use the Python C API have difficulties finding cross-compiled Python3 without the pkgconfig, so make sure we have python3.pc and python-3.7.pc in pkgconfig staging dir. CircleCI requires a package Makefile change to actually do the CI check, so bump PKG_RELEASE. Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
6 years ago
python,python3: Use only target package data for Build/InstallDev This changes Build/InstallDev for both Python 2 and 3 to only copy files from target Python, not from host Python, since InstallDev files are used for target packages to link to other target packages. In particular, usr/lib/python{2.7,3.7}/_sysconfigdata.py holds system configuration data generated at build time, and is different for target Python and host Python. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python3: install pkgconfig to staging Some programs that use the Python C API have difficulties finding cross-compiled Python3 without the pkgconfig, so make sure we have python3.pc and python-3.7.pc in pkgconfig staging dir. CircleCI requires a package Makefile change to actually do the CI check, so bump PKG_RELEASE. Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
6 years ago
python,python3: Include python-config for target Python in InstallDev This installs python{2.7,3.7}-config in $(STAGING_DIR)/usr/bin as part of Build/InstallDev, to be used by other packages to get build configuration for target Python. The treatment for Python 2 and 3 are a bit different: * For Python 2, python-config is a Python script that is expected to be run with, and return data for, the installed Python interpreter. This installs a modified version of this script, to be run using host Python, and read/return data for target Python. * Python 3 includes a shell script version of python-config (expected to be used in cross-compilation scenarios). This simply installs the script into the right place. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python,python3: Move python-config to $(STAGING_DIR)/host Build/InstallDev is passed a second argument, a path where host binaries should be placed (ultimately $(STAGING_DIR)/host). This change moves python[3]-config to that directory. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
​
​
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: introduce libpython3 with ABI_VERSION flag Related to discussion: https://github.com/openwrt/packages/pull/14060 Every once in a while a version bump will occur that requires an ABI change. Example: Python 3.8 to 3.9. When this happens some Python packages would need to be rebuilt. In setups where everything gets rebuilt, this isn't a problem. It's usually a bigger problem when needing to upgrade something via opkg. To accommodate for this, we add a libpython with it's own ABI_VERSION flag. If this ABI_VERSION changes, then this should propagate forward. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 years ago
python: reset packages and start off with minimal python Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python3: introduce libpython3 with ABI_VERSION flag Related to discussion: https://github.com/openwrt/packages/pull/14060 Every once in a while a version bump will occur that requires an ABI change. Example: Python 3.8 to 3.9. When this happens some Python packages would need to be rebuilt. In setups where everything gets rebuilt, this isn't a problem. It's usually a bigger problem when needing to upgrade something via opkg. To accommodate for this, we add a libpython with it's own ABI_VERSION flag. If this ABI_VERSION changes, then this should propagate forward. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 years ago
​
​
​
python3: create ./usr/bin directory at package/install Signed-off-by: Nicolas Thill <nico@openwrt.org>
10 years ago
python3: Change PYTHON_VERSION references to PYTHON3_VERSION PYTHON_VERSION is a holdover from Python 2; all Python 3 variables are prefixed with PYTHON3 (or some variation with "3"). This updates all uses of PYTHON_VERSION to PYTHON3_VERSION. This also sets PYTHON3_PKG_BUILD:=0 before python3-package.mk is included in the python3 Makefile. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
python3: Fix host build tool names recorded in target files Python will record the values of CC, CXX, AR, and READELF (and other configure options) used during compilation. pip will use these programs when asked to compile extension modules on the target device. * If ccache is used during build, CC and CXX will be ccache_cc and ccache_cxx, respectively, which are not available on-device (#11912). * If an external toolchain is used during build, the values of these variables will contain the external toolchain prefix, which may not be available on target. * If the normal toolchain is used during build, AR and READELF will contain the toolchain prefix, but the names of ar and readelf on-device do not contain the prefix; they are named "ar" and "readelf". This changes the values of these variables in Python's files to match the names available on-device, and without any toolchain prefix. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
​
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python,python3: do not package binary files to base packages Thanks to fix 200a5a2eec896b2d34f1114d14df66d810c1f4bd all base packages now contain all binaries that are generated as part of python installation. That causes collision between those packages with package managers that consider this such as Turris updater-ng. This is also just wrong. Those binaries were not included and should not be after mentioned fix as well. This just adds empty install definition. The idea is to override the default one that is otherwise used. Signed-off-by: Karel Kočí <karel.koci@nic.cz>
6 years ago
​
​
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
python3: sync changes from python Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python,python3: Fix host Python compilation for macOS * Remove $$$$(pkg-config --static --libs libcrypto libssl) from HOST_LDFLAGS Having this leads to an "unknown type name 'u_int'" error on Mac. Removing it doesn't appear to affect Python's ability to find buildroot LibreSSL. * Change -Wl,-rpath=... to -Wl,-rpath,... in HOST_LDFLAGS The equals sign version is not supported by the Mac linker (appears to be an GNU extension). The comma version is supported; -rpath and its argument will be separated by a space when passed to the linker. * Add ac_cv_header_libintl_h=no to HOST_CONFIGURE_VARS for Mac Python on Mac doesn't expect to use libintl, but if gettext-full is compiled for host, it will try, leading to undefined symbol errors during compilation. This prevents configure from finding libintl.h. Fixes #7171. Fixes #9621. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
python3: sync changes from python Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python,python3: limit underlinking behavior to linux platforms This change was introduced in commit 1c54e2b0fbe2e9a7d to address build issues on Ubuntu 12.04. However it was reported to cause issues on Mac OS X. Report: https://github.com/openwrt/packages/issues/5310 It was also reported that removing this on MacOS X fixes the issue. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
7 years ago
​
​
​
​
python,python3: Fix host Python compilation for macOS * Remove $$$$(pkg-config --static --libs libcrypto libssl) from HOST_LDFLAGS Having this leads to an "unknown type name 'u_int'" error on Mac. Removing it doesn't appear to affect Python's ability to find buildroot LibreSSL. * Change -Wl,-rpath=... to -Wl,-rpath,... in HOST_LDFLAGS The equals sign version is not supported by the Mac linker (appears to be an GNU extension). The comma version is supported; -rpath and its argument will be separated by a space when passed to the linker. * Add ac_cv_header_libintl_h=no to HOST_CONFIGURE_VARS for Mac Python on Mac doesn't expect to use libintl, but if gettext-full is compiled for host, it will try, leading to undefined symbol errors during compilation. This prevents configure from finding libintl.h. Fixes #7171. Fixes #9621. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
​
python3: Fix target python-config when building on macOS The Python version of python-config is installed when building on macOS, rather than the shell script version when building on Linux. When run on macOS, the Python version of python-config will return values with Mac-specific customizations. This patches the python-config install recipe so that which version is installed can be controlled by the package makefile. When building on macOS, this installs the Python version for host Python and the shell script version for target Python. This also updates Host/Compile and Host/Install to use the default host build recipes, so that the various HOST_* variables are taken into account automatically. Fixes https://github.com/openwrt/packages/issues/14652 Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 years ago
​
python,python3: Fix host Python compilation for macOS * Remove $$$$(pkg-config --static --libs libcrypto libssl) from HOST_LDFLAGS Having this leads to an "unknown type name 'u_int'" error on Mac. Removing it doesn't appear to affect Python's ability to find buildroot LibreSSL. * Change -Wl,-rpath=... to -Wl,-rpath,... in HOST_LDFLAGS The equals sign version is not supported by the Mac linker (appears to be an GNU extension). The comma version is supported; -rpath and its argument will be separated by a space when passed to the linker. * Add ac_cv_header_libintl_h=no to HOST_CONFIGURE_VARS for Mac Python on Mac doesn't expect to use libintl, but if gettext-full is compiled for host, it will try, leading to undefined symbol errors during compilation. This prevents configure from finding libintl.h. Fixes #7171. Fixes #9621. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Enable compile-time optimizations This adds the --enable-optimizations configure option (for profile-guided optimization) for both host and target Python, and the --with-lto configure option (for link-time optimization) for target Python (for non-MIPS platforms). Currently, compiling Python with LTO leads to link errors on mips and mipsel. (Compiling with LTO appears to succeed on mips64 but there is only one mips64 target available for convenient testing.) This also cleans up the host and target configure options: * Sort options/variables - Alphabetically - Flags/options before child-process environment variables - Group options by type (enable/disable/with/without) - Static options/variables before conditional ones * Remove the prefix/dir options, as they are the same as the defaults set by the build system * Remove --with-threads, as it is no longer a valid option (threads are always enabled) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
5 years ago
​
​
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: sync changes from python Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python,python3: Disable user site-packages for host Python Normally, Python will include the user's site-packages directory (~/.local/lib/python$(PYTHON_VERSION)/site-packages) in it's internal search path for modules. This disables this default inclusion for host Python. This change is applied during Host/Configure instead of as a patch to keep this setting unchanged for target Python. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
​
​
​
​
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: Fix target python-config when building on macOS The Python version of python-config is installed when building on macOS, rather than the shell script version when building on Linux. When run on macOS, the Python version of python-config will return values with Mac-specific customizations. This patches the python-config install recipe so that which version is installed can be controlled by the package makefile. When building on macOS, this installs the Python version for host Python and the shell script version for target Python. This also updates Host/Compile and Host/Install to use the default host build recipes, so that the various HOST_* variables are taken into account automatically. Fixes https://github.com/openwrt/packages/issues/14652 Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 years ago
​
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
python,python3: Record PKG_RELEASE for host setuptools/pip This changes the "patched" indicator files for host setuptools and pip to include their PKG_RELEASE values. This also removes host setuptools and/or pip before host install, if the installed copy does not match the version (and PKG_RELEASE) of the copy to be installed. This will allow added or removed patches to affect host setuptools / pip, since these changes will cause PKG_RELEASE to be incremented. This also fixes the host install error, when the install tries to patch an already patched copy of setuptools. (This error occurs because the existing indicator files do not have version numbers in their file names, whereas host install expected version numbers to be present.) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
python3: Fix target python-config when building on macOS The Python version of python-config is installed when building on macOS, rather than the shell script version when building on Linux. When run on macOS, the Python version of python-config will return values with Mac-specific customizations. This patches the python-config install recipe so that which version is installed can be controlled by the package makefile. When building on macOS, this installs the Python version for host Python and the shell script version for target Python. This also updates Host/Compile and Host/Install to use the default host build recipes, so that the various HOST_* variables are taken into account automatically. Fixes https://github.com/openwrt/packages/issues/14652 Signed-off-by: Jeffery To <jeffery.to@gmail.com>
4 years ago
python,python3: Record PKG_RELEASE for host setuptools/pip This changes the "patched" indicator files for host setuptools and pip to include their PKG_RELEASE values. This also removes host setuptools and/or pip before host install, if the installed copy does not match the version (and PKG_RELEASE) of the copy to be installed. This will allow added or removed patches to affect host setuptools / pip, since these changes will cause PKG_RELEASE to be incremented. This also fixes the host install error, when the install tries to patch an already patched copy of setuptools. (This error occurs because the existing indicator files do not have version numbers in their file names, whereas host install expected version numbers to be present.) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python,python3: Allow upgraded host setuptools/pip to be patched This adds the current setuptools/pip version numbers to the indicator files' names, which should allow upgraded versions to be patched. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python,python3: Record PKG_RELEASE for host setuptools/pip This changes the "patched" indicator files for host setuptools and pip to include their PKG_RELEASE values. This also removes host setuptools and/or pip before host install, if the installed copy does not match the version (and PKG_RELEASE) of the copy to be installed. This will allow added or removed patches to affect host setuptools / pip, since these changes will cause PKG_RELEASE to be incremented. This also fixes the host install error, when the install tries to patch an already patched copy of setuptools. (This error occurs because the existing indicator files do not have version numbers in their file names, whereas host install expected version numbers to be present.) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python,python3: Allow upgraded host setuptools/pip to be patched This adds the current setuptools/pip version numbers to the indicator files' names, which should allow upgraded versions to be patched. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python,python3: Record PKG_RELEASE for host setuptools/pip This changes the "patched" indicator files for host setuptools and pip to include their PKG_RELEASE values. This also removes host setuptools and/or pip before host install, if the installed copy does not match the version (and PKG_RELEASE) of the copy to be installed. This will allow added or removed patches to affect host setuptools / pip, since these changes will cause PKG_RELEASE to be incremented. This also fixes the host install error, when the install tries to patch an already patched copy of setuptools. (This error occurs because the existing indicator files do not have version numbers in their file names, whereas host install expected version numbers to be present.) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python3: bump version to 3.9.7 Refreshed patches. And apply hack for line-endings in pep517 (from pip). Hack comment: # FIXME: [1] get rid of this asap; 'patch' doesn't like Windows endings, and this file is full of them... # I actually tried this in a number of ways and the only way to fix this is to implement # a poor-man's dos2unix using sed. # The issue is with the pip package; it seems that it throws in some Windows line-endings # and 'patch' won't handle them. So, we do a "dos2unix" and then patch. # We can get rid of this once this is solved upstream and in pip: # https://github.com/pypa/pep517/pull/130 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
3 years ago
​
python,python3: Allow upgraded host setuptools/pip to be patched This adds the current setuptools/pip version numbers to the indicator files' names, which should allow upgraded versions to be patched. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python,python3: Record PKG_RELEASE for host setuptools/pip This changes the "patched" indicator files for host setuptools and pip to include their PKG_RELEASE values. This also removes host setuptools and/or pip before host install, if the installed copy does not match the version (and PKG_RELEASE) of the copy to be installed. This will allow added or removed patches to affect host setuptools / pip, since these changes will cause PKG_RELEASE to be incremented. This also fixes the host install error, when the install tries to patch an already patched copy of setuptools. (This error occurs because the existing indicator files do not have version numbers in their file names, whereas host install expected version numbers to be present.) Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python,python3: Allow upgraded host setuptools/pip to be patched This adds the current setuptools/pip version numbers to the indicator files' names, which should allow upgraded versions to be patched. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
6 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
​
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
​
python3: split source packages away from compiled packages Same as for python. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
​
python3: introduce libpython3 with ABI_VERSION flag Related to discussion: https://github.com/openwrt/packages/pull/14060 Every once in a while a version bump will occur that requires an ABI change. Example: Python 3.8 to 3.9. When this happens some Python packages would need to be rebuilt. In setups where everything gets rebuilt, this isn't a problem. It's usually a bigger problem when needing to upgrade something via opkg. To accommodate for this, we add a libpython with it's own ABI_VERSION flag. If this ABI_VERSION changes, then this should propagate forward. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
4 years ago
​
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: suffix vars with 3
10 years ago
python: import package as-is from old packages Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: sync build rules with python's Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
python3: replicate packaging work done in python package Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
10 years ago
rename package name to python3
10 years ago
python3: split source packages away from compiled packages Same as for python. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
8 years ago
​
​
 
  1. #

  2. # Copyright (C) 2006-2016 OpenWrt.org

  3. #

  4. # This is free software, licensed under the GNU General Public License v2.

  5. # See /LICENSE for more information.

  6. #

  7. 

  8. include $(TOPDIR)/rules.mk
  9. 

  10. # The file included below defines PYTHON3_VERSION

  11. include ../python3-version.mk
  12. 

  13. PKG_NAME:=python3
  14. PKG_RELEASE:=2
  15. PKG_VERSION:=$(PYTHON3_VERSION).$(PYTHON3_VERSION_MICRO)
  16. 

  17. PKG_SOURCE:=Python-$(PKG_VERSION).tar.xz
  18. PKG_SOURCE_URL:=https://www.python.org/ftp/python/$(PKG_VERSION)
  19. # FIXME: if updating, get rid of [1] & [2] asap

  20. PKG_HASH:=f8145616e68c00041d1a6399b76387390388f8359581abc24432bb969b5e3c57
  21. 

  22. PKG_MAINTAINER:=Alexandru Ardelean <ardeleanalex@gmail.com>, Jeffery To <jeffery.to@gmail.com>
  23. PKG_LICENSE:=Python/2.0
  24. PKG_LICENSE_FILES:=LICENSE Doc/copyright.rst Doc/license.rst Modules/_ctypes/darwin/LICENSE Modules/_ctypes/libffi_osx/LICENSE Modules/expat/COPYING
  25. PKG_CPE_ID:=cpe:/a:python:python
  26. 

  27. # This file provides the necsessary host build variables

  28. include ../python3-host.mk
  29. 

  30. # For Py3Package

  31. PYTHON3_PKG_BUILD:=0
  32. include ../python3-package.mk
  33. 

  34. PKG_FIXUP:=autoreconf
  35. PKG_INSTALL:=1
  36. PKG_BUILD_PARALLEL:=1
  37. HOST_BUILD_PARALLEL:=1
  38. 

  39. PKG_BUILD_DIR:=$(BUILD_DIR)/Python-$(PKG_VERSION)
  40. HOST_BUILD_DIR:=$(BUILD_DIR_HOST)/Python-$(PKG_VERSION)
  41. 

  42. PKG_CONFIG_DEPENDS:= \

  43. 	CONFIG_PACKAGE_python3-pkg-resources \

  44. 	CONFIG_PACKAGE_python3-setuptools CONFIG_PACKAGE_python3-pip
  45. 

  46. PKG_BUILD_DEPENDS:=bluez python3/host
  47. HOST_BUILD_DEPENDS:=bzip2/host libffi/host
  48. 

  49. include $(INCLUDE_DIR)/host-build.mk
  50. include $(INCLUDE_DIR)/package.mk
  51. 

  52. define Package/python3/Default
  53.   SUBMENU:=Python
  54.   SECTION:=lang
  55.   CATEGORY:=Languages
  56.   TITLE:=Python $(PYTHON3_VERSION) programming language
  57.   URL:=https://www.python.org/
  58. endef
  59. 

  60. define Package/python3/Default/description
  61.  Python is a dynamic object-oriented programming language that can be used
  62.  for many kinds of software development. It offers strong support for
  63.  integration with other languages and tools, comes with extensive standard
  64.  libraries, and can be learned in a few days. Many Python programmers
  65.  report substantial productivity gains and feel the language encourages
  66.  the development of higher quality, more maintainable code.
  67. endef
  68. 

  69. define Package/libpython3
  70. $(call Package/python3/Default)
  71.   TITLE:=Python $(PYTHON3_VERSION) core library
  72.   DEPENDS:=+libpthread +zlib
  73.   ABI_VERSION:=$(PYTHON3_VERSION)
  74. endef
  75. 

  76. define Package/libpython3/description
  77.   This package contains only core Python library.
  78. endef
  79. 

  80. define Package/python3-base
  81. $(call Package/python3/Default)
  82.   TITLE:=Python $(PYTHON3_VERSION) interpreter
  83.   DEPENDS:=+libpthread +zlib +libpython3
  84. endef
  85. 

  86. define Package/python3-base/description
  87.   This package contains only the interpreter and the bare minimum
  88.   for the interpreter to start.
  89. endef
  90. 

  91. define Package/python3-light
  92. $(call Package/python3/Default)
  93.   TITLE:=Python $(PYTHON3_VERSION) light installation
  94.   DEPENDS:=+python3-base +libffi +libbz2 +libuuid
  95. endef
  96. 

  97. define Package/python3-light/config
  98.   source "$(SOURCE)/Config-python3-light.in"
  99. endef
  100. 

  101. define Package/python3-light/description
  102.   This package is essentially the python3-base package plus
  103.   a few of the rarely used (and big) libraries stripped out
  104.   into separate packages.
  105. endef
  106. 

  107. PYTHON3_LIB_FILES_DEL:=
  108. PYTHON3_PACKAGES:=
  109. PYTHON3_SO_SUFFIX:=cpython-$(PYTHON3_VERSION_MAJOR)$(PYTHON3_VERSION_MINOR).so
  110. PYTHON3_PACKAGES_DEPENDS:=
  111. define Py3BasePackage
  112.   PYTHON3_PACKAGES+=$(1)
  113.   ifeq ($(3),)
  114.     PYTHON3_PACKAGES_DEPENDS+=$(1)
  115.   endif
  116.   PYTHON3_LIB_FILES_DEL+=$(2)
  117.   define Py3Package/$(1)/filespec
  118.     ifneq ($(2),)
  119.       $(subst $(space),$(newline),$(foreach lib_file,$(2),+|$(lib_file)))
  120.       -|/usr/lib/python$(PYTHON3_VERSION)/*/test
  121.       -|/usr/lib/python$(PYTHON3_VERSION)/*/tests
  122.     endif
  123.   endef
  124.   Py3Package/$(1)/install?=:
  125. endef
  126. 

  127. include ./files/python3-package-*.mk
  128. 

  129. define Package/python3
  130. $(call Package/python3/Default)
  131.   DEPENDS:=+python3-light $(foreach package,$(PYTHON3_PACKAGES_DEPENDS),+$(package))
  132. endef
  133. 

  134. define Package/python3/description
  135.   This package contains the (almost) full Python install.
  136.   It's python3-light + all other packages.
  137. endef
  138. 

  139. TARGET_CONFIGURE_OPTS+= \

  140. 	READELF="$(TARGET_CROSS)readelf"
  141. 

  142. MAKE_FLAGS+=\

  143. 	LD="$(TARGET_CC)"
  144. 

  145. EXTRA_CFLAGS+= \

  146. 	-DNDEBUG -fno-inline
  147. EXTRA_LDFLAGS+= \

  148. 	-L$(PKG_BUILD_DIR) \

  149. 	-L$(STAGING_DIR)/usr/lib -L$(STAGING_DIR)/lib
  150. 

  151. CONFIGURE_ARGS+= \

  152. 	--enable-optimizations \

  153. 	--enable-shared \

  154. 	--with-system-ffi \

  155. 	--without-cxx-main \

  156. 	--without-ensurepip \

  157. 	--without-pymalloc \

  158. 	$(if $(CONFIG_IPV6),--enable-ipv6) \

  159. 	$(if $(findstring mips,$(CONFIG_ARCH)),,--with-lto) \

  160. 	CONFIG_SITE="$(PKG_BUILD_DIR)/config.site" \

  161. 	OPT="$(TARGET_CFLAGS)"
  162. 

  163. define Build/Prepare
  164. 	$(call Build/Prepare/Default)
  165. 	$(CP) ./files/config.site $(PKG_BUILD_DIR)/config.site
  166. endef
  167. 

  168. ifdef CONFIG_PACKAGE_python3-setuptools
  169. PYTHON3_SETUPTOOLS_BUILD:=1
  170. endif
  171. 

  172. ifdef CONFIG_PACKAGE_python3-pkg-resources
  173. PYTHON3_SETUPTOOLS_BUILD:=1
  174. endif
  175. 

  176. ifeq ($(PYTHON3_SETUPTOOLS_BUILD),1)
  177. define Build/Compile/python3-setuptools
  178. 	$(HOST_PYTHON3_PIP) \

  179. 		--disable-pip-version-check \

  180. 		--cache-dir "$(DL_DIR)/pip-cache" \

  181. 		install \

  182. 		--ignore-installed \

  183. 		--root=$(PKG_BUILD_DIR)/install-setuptools \

  184. 		--prefix=/usr \

  185. 		$(PKG_BUILD_DIR)/Lib/ensurepip/_bundled/setuptools-$(PYTHON3_SETUPTOOLS_VERSION)-py3-none-any.whl
  186. 	$(call PatchDir,$(PKG_BUILD_DIR)/install-setuptools/usr/lib/python$(PYTHON3_VERSION)/site-packages,./patches-setuptools,)
  187. endef
  188. else
  189. define Build/Compile/python3-setuptools
  190. 	ls $(PKG_BUILD_DIR)/Lib/ensurepip/_bundled/setuptools-$(PYTHON3_SETUPTOOLS_VERSION)-py3-none-any.whl
  191. endef
  192. endif # CONFIG_PACKAGE_python3-setuptools

  193. 

  194. ifdef CONFIG_PACKAGE_python3-pip
  195. define Build/Compile/python3-pip
  196. 	$(HOST_PYTHON3_PIP) \

  197. 		--disable-pip-version-check \

  198. 		--cache-dir "$(DL_DIR)/pip-cache" \

  199. 		install \

  200. 		--ignore-installed \

  201. 		--root=$(PKG_BUILD_DIR)/install-pip \

  202. 		--prefix=/usr \

  203. 		$(PKG_BUILD_DIR)/Lib/ensurepip/_bundled/pip-$(PYTHON3_PIP_VERSION)-py3-none-any.whl
  204. 	# FIXME: [1] get rid of this asap; 'patch' doesn't like Windows endings, and this file is full of them...
  205. 	#        I actually tried this in a number of ways and the only way to fix this is to implement
  206. 	#        a poor-man's dos2unix using sed.
  207. 	#        The issue is with the pip package; it seems that it throws in some Windows line-endings
  208. 	#        and 'patch' won't handle them. So, we do a "dos2unix" and then patch.
  209. 	#        We can get rid of this once this is solved upstream and in pip:
  210. 	#            https://github.com/pypa/pep517/pull/130
  211. 	sed 's/\r//' -i $(PKG_BUILD_DIR)/install-pip/usr/lib/python$(PYTHON3_VERSION)/site-packages/pip/_vendor/pep517/in_process/__init__.py
  212. 	$(call PatchDir,$(PKG_BUILD_DIR)/install-pip/usr/lib/python$(PYTHON3_VERSION)/site-packages,./patches-pip,)
  213. endef
  214. else
  215. define Build/Compile/python3-pip
  216. 	ls $(PKG_BUILD_DIR)/Lib/ensurepip/_bundled/pip-$(PYTHON3_PIP_VERSION)-py3-none-any.whl
  217. endef
  218. endif # CONFIG_PACKAGE_python3-pip

  219. 

  220. define Build/Compile
  221. 	$(call Build/Compile/Default)
  222. 	# Use host pip to install python-setuptools
  223. 	$(call Build/Compile/python3-setuptools)
  224. 	$(call Build/Compile/python3-pip)
  225. endef
  226. 

  227. define Build/InstallDev
  228. 	$(INSTALL_DIR) $(1)/usr/include $(1)/usr/lib $(1)/usr/lib/pkgconfig
  229. 	$(INSTALL_DIR) $(2)/bin
  230. 	$(CP) \

  231. 		$(PKG_INSTALL_DIR)/usr/include/python$(PYTHON3_VERSION) \

  232. 		$(1)/usr/include/
  233. 	$(CP) \

  234. 		$(PKG_INSTALL_DIR)/usr/lib/python$(PYTHON3_VERSION) \

  235. 		$(PKG_INSTALL_DIR)/usr/lib/libpython$(PYTHON3_VERSION).so* \

  236. 		$(1)/usr/lib/
  237. 	grep \

  238. 		'^_PYTHON_HOST_PLATFORM=' \

  239. 		$(PKG_INSTALL_DIR)/usr/lib/python$(PYTHON3_VERSION)/config-$(PYTHON3_VERSION)/Makefile > \

  240. 		$(1)/usr/lib/python$(PYTHON3_VERSION)/config-$(PYTHON3_VERSION)/Makefile-vars
  241. 	$(CP) \

  242. 		$(PKG_INSTALL_DIR)/usr/lib/pkgconfig/python*.pc \

  243. 		$(1)/usr/lib/pkgconfig
  244. 	$(INSTALL_BIN) \

  245. 		$(PKG_INSTALL_DIR)/usr/bin/python$(PYTHON3_VERSION)-config \

  246. 		$(2)/bin/
  247. 	$(SED) \

  248. 		's|^prefix_real=.*$$$$|prefix_real="$(PYTHON3_DIR)"|' \

  249. 		$(2)/bin/python$(PYTHON3_VERSION)-config
  250. endef
  251. 

  252. PYTHON3_BASE_LIB_FILES:= \

  253. 	/usr/lib/python$(PYTHON3_VERSION)/encodings \

  254. 	/usr/lib/python$(PYTHON3_VERSION)/_collections_abc.py \

  255. 	/usr/lib/python$(PYTHON3_VERSION)/_sitebuiltins.py \

  256. 	/usr/lib/python$(PYTHON3_VERSION)/_sysconfigdata.py \

  257. 	/usr/lib/python$(PYTHON3_VERSION)/_weakrefset.py \

  258. 	/usr/lib/python$(PYTHON3_VERSION)/abc.py \

  259. 	/usr/lib/python$(PYTHON3_VERSION)/codecs.py \

  260. 	/usr/lib/python$(PYTHON3_VERSION)/genericpath.py \

  261. 	/usr/lib/python$(PYTHON3_VERSION)/io.py \

  262. 	/usr/lib/python$(PYTHON3_VERSION)/os.py \

  263. 	/usr/lib/python$(PYTHON3_VERSION)/posixpath.py \

  264. 	/usr/lib/python$(PYTHON3_VERSION)/site.py \

  265. 	/usr/lib/python$(PYTHON3_VERSION)/sysconfig.py \

  266. 	/usr/lib/python$(PYTHON3_VERSION)/stat.py
  267. 

  268. PYTHON3_LIB_FILES_DEL+=$(PYTHON3_BASE_LIB_FILES)
  269. 

  270. define Py3Package/python3-base/filespec
  271. +|/usr/bin/python$(PYTHON3_VERSION)
  272. $(subst $(space),$(newline),$(foreach lib_file,$(PYTHON3_BASE_LIB_FILES),+|$(lib_file)))
  273. endef
  274. 

  275. define Py3Package/python3-light/filespec
  276. +|/usr/lib/python$(PYTHON3_VERSION)
  277. -|/usr/lib/python$(PYTHON3_VERSION)/distutils/cygwinccompiler.py
  278. -|/usr/lib/python$(PYTHON3_VERSION)/distutils/command/wininst*
  279. -|/usr/lib/python$(PYTHON3_VERSION)/ensurepip
  280. -|/usr/lib/python$(PYTHON3_VERSION)/idlelib
  281. -|/usr/lib/python$(PYTHON3_VERSION)/tkinter
  282. -|/usr/lib/python$(PYTHON3_VERSION)/turtledemo
  283. -|/usr/lib/python$(PYTHON3_VERSION)/lib-dynload/_test*.so
  284. -|/usr/lib/python$(PYTHON3_VERSION)/pdb.doc
  285. -|/usr/lib/python$(PYTHON3_VERSION)/test
  286. -|/usr/lib/python$(PYTHON3_VERSION)/webbrowser.py
  287. -|/usr/lib/python$(PYTHON3_VERSION)/*/test
  288. -|/usr/lib/python$(PYTHON3_VERSION)/*/tests
  289. -|/usr/lib/python$(PYTHON3_VERSION)/_osx_support.py
  290. $(subst $(space),$(newline),$(foreach lib_file,$(PYTHON3_LIB_FILES_DEL),-|$(lib_file)))
  291. endef
  292. 

  293. define Package/libpython3/install
  294. 	# Adding the lib-dynload folder (even just empty) suppresses 2 warnings when starting Python
  295. 	$(INSTALL_DIR) $(1)/usr/lib/python$(PYTHON3_VERSION)/lib-dynload/
  296. 	$(CP) $(PKG_INSTALL_DIR)/usr/lib/libpython$(PYTHON3_VERSION).so* $(1)/usr/lib/
  297. endef
  298. 

  299. define Py3Package/python3-base/install
  300. 	$(INSTALL_DIR) $(1)/usr/bin
  301. 	$(LN) python$(PYTHON3_VERSION) $(1)/usr/bin/python3
  302. 	$(LN) python$(PYTHON3_VERSION) $(1)/usr/bin/python
  303.   # This depends on being called before filespec is processed
  304. 	$(SED) 's|$(TARGET_AR)|ar|g;s|$(TARGET_CROSS)readelf|readelf|g;s|$(TARGET_CC)|gcc|g;s|$(TARGET_CXX)|g++|g' \

  305. 		$(PKG_INSTALL_DIR)/usr/lib/python$(PYTHON3_VERSION)/_sysconfigdata.py
  306. endef
  307. 

  308. Py3Package/python3-light/install:=:
  309. Py3Package/python3/install:=:
  310. 

  311. define Py3Package/python3/filespec
  312. -|$(PYTHON3_PKG_DIR)
  313. endef
  314. 

  315. HOST_LDFLAGS += \

  316. 	-Wl$(comma)-rpath$(comma)$(STAGING_DIR_HOSTPKG)/lib
  317. 

  318. ifeq ($(HOST_OS),Linux)
  319. HOST_LDFLAGS += \

  320. 	-Wl,--no-as-needed -lrt
  321. endif
  322. 

  323. ifeq ($(HOST_OS),Darwin)
  324. HOST_CONFIGURE_VARS += \

  325. 	ac_cv_header_libintl_h=no
  326. HOST_MAKE_VARS += \

  327. 	USE_PYTHON_CONFIG_PY=1
  328. endif
  329. 

  330. HOST_CONFIGURE_ARGS+= \

  331. 	--enable-optimizations \

  332. 	--with-ensurepip=upgrade \

  333. 	--with-system-expat=$(STAGING_DIR_HOSTPKG) \

  334. 	--without-cxx-main \

  335. 	--without-pymalloc \

  336. 	CONFIG_SITE=
  337. 

  338. define Host/Configure
  339. 	$(SED) 's/^ENABLE_USER_SITE = None$$$$/ENABLE_USER_SITE = False/' $(HOST_BUILD_DIR)/Lib/site.py
  340. 	$(call Host/Configure/Default)
  341. endef
  342. 

  343. define Host/Compile
  344. 	$(call Host/Compile/Default,python)
  345. 	$(call Host/Compile/Default,sharedmods)
  346. endef
  347. 

  348. define Host/Install
  349. 	$(if $(wildcard $(HOST_PYTHON3_PKG_DIR)/.setuptools_installed_$(PYTHON3_SETUPTOOLS_VERSION)-$(PYTHON3_SETUPTOOLS_PKG_RELEASE)),,
  350. 		rm -rf \

  351. 			$(HOST_PYTHON3_PKG_DIR)/pkg_resources \

  352. 			$(HOST_PYTHON3_PKG_DIR)/setuptools \

  353. 			$(HOST_PYTHON3_PKG_DIR)/setuptools-* \

  354. 			$(HOST_PYTHON3_PKG_DIR)/.setuptools-patched* \

  355. 			$(HOST_PYTHON3_PKG_DIR)/.setuptools_installed_*
  356. 	)
  357. 	$(if $(wildcard $(HOST_PYTHON3_PKG_DIR)/.pip_installed_$(PYTHON3_PIP_VERSION)-$(PYTHON3_PIP_PKG_RELEASE)),,
  358. 		rm -rf \

  359. 			$(HOST_PYTHON3_PKG_DIR)/pip \

  360. 			$(HOST_PYTHON3_PKG_DIR)/pip-* \

  361. 			$(HOST_PYTHON3_PKG_DIR)/.pip-patched* \

  362. 			$(HOST_PYTHON3_PKG_DIR)/.pip_installed_*
  363. 	)
  364. 	$(call Host/Install/Default)
  365. 	$(if $(wildcard $(HOST_PYTHON3_PKG_DIR)/.setuptools_installed_$(PYTHON3_SETUPTOOLS_VERSION)-$(PYTHON3_SETUPTOOLS_PKG_RELEASE)),,
  366. 		$(call HostPatchDir,$(HOST_PYTHON3_PKG_DIR),./patches-setuptools,)
  367. 		touch $(HOST_PYTHON3_PKG_DIR)/.setuptools_installed_$(PYTHON3_SETUPTOOLS_VERSION)-$(PYTHON3_SETUPTOOLS_PKG_RELEASE)
  368. 	)
  369. 	$(if $(wildcard $(HOST_PYTHON3_PKG_DIR)/.pip_installed_$(PYTHON3_PIP_VERSION)-$(PYTHON3_PIP_PKG_RELEASE)),,
  370. 		# FIXME: [2] get rid of this asap; same as [1]
  371. 		sed 's/\r//' -i $(HOST_PYTHON3_PKG_DIR)/pip/_vendor/pep517/in_process/__init__.py
  372. 		$(call HostPatchDir,$(HOST_PYTHON3_PKG_DIR),./patches-pip,)
  373. 		touch $(HOST_PYTHON3_PKG_DIR)/.pip_installed_$(PYTHON3_PIP_VERSION)-$(PYTHON3_PIP_PKG_RELEASE)
  374. 	)
  375. endef
  376. 

  377. $(eval $(call HostBuild))
  378. 

  379. $(foreach package, $(PYTHON3_PACKAGES),  \
  380. 	$(eval $(call Py3Package,$(package))) \

  381. 	$(eval $(call BuildPackage,$(package))) \

  382. 	$(eval $(call BuildPackage,$(package)-src)) \

  383. )
  384. 

  385. $(eval $(call BuildPackage,libpython3))
  386. 

  387. $(eval $(call Py3Package,python3-base))
  388. $(eval $(call Py3Package,python3-light))
  389. $(eval $(call Py3Package,python3))
  390. 

  391. $(eval $(call BuildPackage,python3-base))
  392. $(eval $(call BuildPackage,python3-light))
  393. $(eval $(call BuildPackage,python3))
  394. 

  395. $(eval $(call BuildPackage,python3-base-src))
  396. $(eval $(call BuildPackage,python3-light-src))