python3: Use regular package recipes for python3 package
There is no need to use Py3Package for python3 as it does not package any Python files; it is an empty package with dependencies to install the full Python installation. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
This commit is contained in:
parent
09e06f9594
commit
87631ecdd4
1 changed files with 2 additions and 7 deletions
|
@ -264,11 +264,7 @@ define Py3Package/python3-base/install
|
||||||
endef
|
endef
|
||||||
|
|
||||||
Py3Package/python3-light/install:=:
|
Py3Package/python3-light/install:=:
|
||||||
Py3Package/python3/install:=:
|
Package/python3/install:=:
|
||||||
|
|
||||||
define Py3Package/python3/filespec
|
|
||||||
-|$(PYTHON3_PKG_DIR)
|
|
||||||
endef
|
|
||||||
|
|
||||||
# libuuid is provided by e2fsprogs and uuid/uuid.h is moved into
|
# libuuid is provided by e2fsprogs and uuid/uuid.h is moved into
|
||||||
# $(STAGING_DIR_HOST)/include/e2fsprogs
|
# $(STAGING_DIR_HOST)/include/e2fsprogs
|
||||||
|
@ -351,14 +347,13 @@ $(foreach package, $(PYTHON3_PACKAGES), \
|
||||||
)
|
)
|
||||||
|
|
||||||
$(eval $(call BuildPackage,libpython3))
|
$(eval $(call BuildPackage,libpython3))
|
||||||
|
$(eval $(call BuildPackage,python3))
|
||||||
|
|
||||||
$(eval $(call Py3Package,python3-base))
|
$(eval $(call Py3Package,python3-base))
|
||||||
$(eval $(call Py3Package,python3-light))
|
$(eval $(call Py3Package,python3-light))
|
||||||
$(eval $(call Py3Package,python3))
|
|
||||||
|
|
||||||
$(eval $(call BuildPackage,python3-base))
|
$(eval $(call BuildPackage,python3-base))
|
||||||
$(eval $(call BuildPackage,python3-light))
|
$(eval $(call BuildPackage,python3-light))
|
||||||
$(eval $(call BuildPackage,python3))
|
|
||||||
|
|
||||||
$(eval $(call BuildPackage,python3-base-src))
|
$(eval $(call BuildPackage,python3-base-src))
|
||||||
$(eval $(call BuildPackage,python3-light-src))
|
$(eval $(call BuildPackage,python3-light-src))
|
||||||
|
|
Loading…
Reference in a new issue