aboutsummaryrefslogtreecommitdiff
path: root/lang/python/python-package.mk
Commit message (Collapse)AuthorAge
* python,python3: fix recursive deps caused by dangling DEPENDSAlexandru Ardelean2018-01-17
| | | | | | | For python `src` packages we should clear out the DEPENDS to prevent recursive deps from happening. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* Merge pull request #5457 from jefferyto/python-pkg-setup-args-varsHannu Nyman2018-01-17
|\ | | | | python,python3: add vars to customize setup arguments / variables
| * python,python3: add vars to customize setup arguments / variablesJeffery To2018-01-16
| | | | | | | | | | | | | | | | | | | | | | | | | | This adds: * PYTHON_PKG_SETUP_ARGS * PYTHON_PKG_SETUP_VARS * PYTHON3_PKG_SETUP_ARGS * PYTHON3_PKG_SETUP_VARS to customize Python package setup arguments / environment variables. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* | python,python3: disable dependencies between python src packagesAlexandru Ardelean2018-01-16
|/ | | | | | | Related to: https://github.com/openwrt/packages/issues/5424 Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python,python3: merge package install scriptsAlexandru Ardelean2018-01-10
| | | | | | | | | | | | | The only difference just a parameter for Python3 [ -b to compile bytecodes in legacy mode ]. No need to keep 2 almost identical files now that they're exported. I'm a bit scared of that param, since it may get removed at some point. But let's see until then. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python,python3: simplify path to install shell-scriptAlexandru Ardelean2018-01-10
| | | | | | | Now that all files are exported, it makes sense to just reference the script directly. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* python,python3: export mk files outside of python package dirsAlexandru Ardelean2018-01-10
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>