staging/nbd/include/image.mk, branch master

image: support generating per device targz rootfs

2026-02-09T15:43:29Z

Currently, for targets that use the CONFIG_TARGET_ROOTFS_TARGZ a single rootfs tarball is generated for the subtarget based of $(TARGET_DIR). However, this means that it does not respect DEVICE_PACKAGES like other rootfs images. So, lets augment CONFIG_TARGET_ROOTFS_TARGZ by adding a proper targz fstype so that per device rootfs is generated under lock. This is required so that devices that use custom sysupgrade archives like Methode devices, can actually include a per device rootfs so when building for multiple devices and with CONFIG_TARGET_PER_DEVICE_ROOTFS set the built image actually includes the listed DEVICE_PACKAGES. Signed-off-by: Robert Marko

image: add CONFIG_EXTRA_IMAGE_NAME

2025-12-12T22:06:06Z

This allows an optional tag to be put in the .config file which is included in the filename of the resulting images, so it's easier to build images with different functionality for the same target hardware. Signed-off-by: David Woodhouse Link: https://github.com/openwrt/openwrt/pull/20984 Signed-off-by: Petr Štetiar

build: remove iwinfo dependency

2025-09-27T20:04:57Z

Do not always try to include iwinfo in the images when wpa supplicant or Broadcom nas is also included. iwinfo is incompatible with current default configuration. iwinfo is only build when CONFIG_WIFI_SCRIPTS_UCODE is not set. If CONFIG_WIFI_SCRIPTS_UCODE is not set kmod-cfg80211 depends on iwinfo, so it should be included in all images with wifi drivers. The CONFIG_WIFI_SCRIPTS_UCODE option was recently changed to be active by default. This should fix the current buildbot build failures. This reverts commit 6435b8bb27ea ("build: include iwinfo by default if nas or wpad(-mini) is selected") Fixes: 04e9929c47e9 ("wifi-scripts: enable ucode scripts by default") Link: https://github.com/openwrt/openwrt/pull/20211 Signed-off-by: Hauke Mehrtens

image: only calculate EROFS_PCLUSTERSIZE when needed

2025-07-06T08:32:44Z

Fixes shell warning on any makefile including image.mk when EROFS is not enabled Signed-off-by: Felix Fietkau

image: add support for EROFS rootfs image generation

2025-07-05T13:24:54Z

Add support for generating EROFS rootfs images. The EROFS filesystem can offer competitive I/O performance while minimizing final image size when using the MicroLZMA compressor. Target platform: linux-x86_generic (target-i386_pentium4_musl) Filesystem Image Size ============= ========== root.erofs 4882432 root.ext4 109051904 root.squashfs 4903302 Co-Developed-by: Gao Xiang Signed-off-by: Gao Xiang Link: https://github.com/openwrt/openwrt/pull/19244 Signed-off-by: Christian Marangi

build: image: support specifying mksquashfs4 parallel threads

2025-06-05T19:28:03Z

By enabling multi-threading file reading, the squashfs rootfs build process can be greatly accelerated. We use 4 as the default thread number. This is the default value for squashfs4 tool 4.7 if we don't append "-block-readers" or "-small-readers" options. For more test results: https://github.com/plougher/squashfs-tools/blob/4.7/Documentation/4.7/README Signed-off-by: Shiji Yang Link: https://github.com/openwrt/openwrt/pull/19019 Signed-off-by: Nick Hainke

image: only filter out images when ImageBuilder is used

2025-05-24T10:24:48Z

Currently, we are filtering out images if DEFAULT:=n or BROKEN:=y are set, so if you are building from scratch and want to build custom images that are stripped down to fit, you must edit the image recipe or its just filtered out. So, to allow this behaviour when building from scratch as we can assume that person doing that knows what they are attempting to do lets just limit the filtering to ImageBuilder. Fixes: f060615a78e5 ("image: respect DEFAULT and BROKEN when Default profile is selected") Signed-off-by: Robert Marko

image: respect DEFAULT and BROKEN when Default profile is selected

2025-05-16T17:40:36Z

Currently, when you select the Default profile it does not honor DEFAULT:=n nor BROKEN:=y in device profiles but rather just tries to build all of them. This may work when building directly, but when using Image Builder it will always fail since no kernel or anything else is present for devices that have DEFAULT:=n or BROKEN:=Y set since those are skipped during build. So, lets look for DEFAULT being set to "n" or BROKEN being set to "y" and then remove clear _PROFILE_SET so they dont end up being marked for installation. Fixes: #18410 Link: https://github.com/openwrt/openwrt/pull/18814 Signed-off-by: Robert Marko

build: include size-limits to device-metadata

2025-04-18T12:00:39Z

Include the image and kernel size limitations defined for each device to the device metadata JSON. These informations are only added if defined. Signed-off-by: David Bauer

image: apk: dont fail on removing a package that doesnt exist

2024-11-29T10:31:56Z

Currently, in case when a package in the device package list is marked with the "-"" prefix meaning that its supposed to be removed for that device but it was not actually previously built it will cause the APK to error out it and thus image generation will also fail. So, lets do what OPKG build step does and supress the error with the "-" prefix in make. Fixes: #17103 Fixes: d788ab376f85 ("build: add APK package build capabilities") Link: https://github.com/openwrt/openwrt/pull/17106 Signed-off-by: Robert Marko