summaryrefslogtreecommitdiff
path: root/lang/python/python3/files/python3-package.mk
diff options
context:
space:
mode:
authorAlexandru Ardelean <ardeleanalex@gmail.com>2017-07-04 20:58:37 +0300
committerAlexandru Ardelean <ardeleanalex@gmail.com>2017-07-07 18:07:10 +0300
commit8db8c927edb277f7ff2c6147530cd28f1e4c5d8c (patch)
treed8944b969ec31394522c51a604bb3bda41279434 /lang/python/python3/files/python3-package.mk
parent2705d032bb61bb028575a86338b6d9f21230423b (diff)
python,python3: define PyBuild/Compile & Py3Build/Compile
Similar to LEDE/OpenWrt's Build/Compile/Default rule, and other similarities like this. This should allow Python packages to define PyBuild/Compile rules to do specific stuff per package. The advantage of using these (over just overriding Build/Compile) is the VARIANT mechanism that is in place to support packaging both for Python & Python3. So, PyBuild/Compile will get picked up for the Python variant build, and Py3Build/Compile will get picked up for the Python3 variant build. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Diffstat (limited to 'lang/python/python3/files/python3-package.mk')
-rw-r--r--lang/python/python3/files/python3-package.mk4
1 files changed, 3 insertions, 1 deletions
diff --git a/lang/python/python3/files/python3-package.mk b/lang/python/python3/files/python3-package.mk
index 36a030c02..22ee527a1 100644
--- a/lang/python/python3/files/python3-package.mk
+++ b/lang/python/python3/files/python3-package.mk
@@ -132,8 +132,10 @@ define Py3Build/Compile/Default
)
endef
+Py3Build/Compile=$(Py3Build/Compile/Default)
+
ifeq ($(BUILD_VARIANT),python3)
define Build/Compile
- $(call Py3Build/Compile/Default)
+ $(call Py3Build/Compile)
endef
endif # python3