From: Pushpal Sidhu <[email protected]> A few linux BSP's create a manifest file of installed packages for a given target in order to help them understand exactly what's on their images. Create one here as well as a build artifact since many users have an affinity to prune down on packages to save valuable flash space.
Signed-off-by: Pushpal Sidhu <[email protected]> Signed-off-by: Tim Harvey <[email protected]> --- include/image.mk | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/include/image.mk b/include/image.mk index 7079f18..bab7f53 100644 --- a/include/image.mk +++ b/include/image.mk @@ -264,6 +264,13 @@ define Image/mkfs/prepare $(call Image/mkfs/prepare/default,$(1)) endef +define Image/Manifest + $(STAGING_DIR_HOST)/bin/opkg \ + --offline-root $(TARGET_DIR) \ + --add-arch all:100 \ + --add-arch $(if $(ARCH_PACKAGES),$(ARCH_PACKAGES),$(BOARD)):200 list-installed > \ + $(BIN_DIR)/$(IMG_PREFIX)$(if $(PROFILE_SANITIZED),-$(PROFILE_SANITIZED)).manifest +endef ifdef CONFIG_TARGET_ROOTFS_TARGZ define Image/Build/targz @@ -565,5 +572,6 @@ define BuildImage $(MAKE) legacy-images install: install-images + $(call Image/Manifest) endef -- 1.9.1 _______________________________________________ Lede-dev mailing list [email protected] http://lists.infradead.org/mailman/listinfo/lede-dev
