aboutsummaryrefslogtreecommitdiff
path: root/include/image.mk
Commit message (Collapse)AuthorAge
* image: only calculate EROFS_PCLUSTERSIZE when neededFelix Fietkau2025-07-06
| | | | | | | Fixes shell warning on any makefile including image.mk when EROFS is not enabled Signed-off-by: Felix Fietkau <nbd@nbd.name>
* image: add support for EROFS rootfs image generationGao Xiang2025-07-05
| | | | | | | | | | | | | | | | | | | | 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 <hsiangkao@linux.alibaba.com> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com> Link: https://github.com/openwrt/openwrt/pull/19244 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* build: image: support specifying mksquashfs4 parallel threadsShiji Yang2025-06-05
| | | | | | | | | | | | | | 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 <yangshiji66@outlook.com> Link: https://github.com/openwrt/openwrt/pull/19019 Signed-off-by: Nick Hainke <vincent@systemli.org>
* image: only filter out images when ImageBuilder is usedRobert Marko2025-05-24
| | | | | | | | | | | | | | 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 <robimarko@gmail.com>
* image: respect DEFAULT and BROKEN when Default profile is selectedRobert Marko2025-05-16
| | | | | | | | | | | | | | | | | 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 <robimarko@gmail.com>
* build: include size-limits to device-metadataDavid Bauer2025-04-18
| | | | | | | | | 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 <mail@david-bauer.net>
* image: apk: dont fail on removing a package that doesnt existRobert Marko2024-11-29
| | | | | | | | | | | | | | | 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 <robimarko@gmail.com>
* image: apk: remove explicit distfeeds handlingPetr Štetiar2024-11-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the build fails due to the following: mv: cannot stat 'linux-mediatek_filogic/target-dir-7872e783/etc/apk/repositories': No such file or directory as the changes done in the commit e031dab93ec3 ("base-files: move apk distfeeds into directory") forget to adapt image generation part. While looking into this, I've realized, that we don't need this explicit handling in the image generating code since the feeds are solely configured by `base-files` and `apk` packages, so those should always provide the correct feeds content, so lets simply drop this unnecessary code. Moving away /etc/opkg is done to prevent opkg from picking up the remote feeds defined from base-files and only use the local feeds, but for apk we explicitly pass --repositories-file which disables parsing of /etc/apk/repositories and /etc/apk/repositories.d, so we do not need to backup anything. Fixes: #16981 Fixes: e031dab93ec3 ("base-files: move apk distfeeds into directory") Reported-by: Chen Minqiang <ptpt52@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz> [jonas.gorski: add an explicit explanation where the original mv comes from and why we don't need it for apk]. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* package: use /dev/null for apk --repositories-fileChristian Marangi2024-11-15
| | | | | | | | | | | In preparation for APK version bump, use /dev/null instead of /dev/zero for --repositories-file to mute an error in recent APK files. New APK version use modern istream logic that are more sensible to the kind of file passed and /dev/null is required to correctly handle an empty repository file. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* build: add comments to makefilesSergey Matsievskiy2024-11-12
| | | | | | | | | | | | | | Add comments to build system makefile functions and variables to help developers in understanding build system internals and ease the development process. This patch adds some documentation examples with proposed doxygen-like syntax. Hopefully, this would start the discussion and result in generation of the makefile documentation guidelines. Signed-off-by: Sergey Matsievskiy <matsievskiysv@gmail.com> Link: https://github.com/openwrt/openwrt/pull/16888 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* build: correctly ignore Initramfs image on errorChristian Marangi2024-10-30
| | | | | | | | | Correctly ignore Initramfs image copy on error. This follows the pattern with sysupgrade image where an image might fail as it's too big or the generation command fails and there is nothing to copy to the bin directory. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* build: introduce support to declare skip packageChristian Marangi2024-10-29
| | | | | | | | | | | | | | | | It seems some target started declaring package in DEVICE_PACKAGES just to call InstallDev and generate binary for the image firmware. This is very much used by layerscape target where trusted-firmware-a and dependency are called for final image generation. This is problematic for APK since it's more sensible to non exisiting package. To handle this, introduce a prefix '~' for a package that will signal to build the package but not install it in the final image. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* build: detach apk repository handling from rootfs.mkChristian Marangi2024-10-29
| | | | | | | | | To better support imagebuilder declaring --repositories-file on calling apk macro, detach this and --repository from rootfs.mk macro and move it to package Makefile and image.mk where they are used to permit a more generic usage. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* image: exclude initramfs-images dependency with IBChristian Marangi2024-07-09
| | | | | | | | Exclude initramfs-images dependency with IB as the target is not defined in such context. Fixes: cc6a0abcabf7 ("image: make images and artifacts dependent of initramfs") Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* image: make images and artifacts dependent of initramfsChristian Marangi2024-07-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is currently a BIG bug in how the images dependency is handled and recent Per Device Rootfs made this more clear and less statistical. There is currently no dependency between images/artifacts build with initramfs build. This cause whatever additional image that depends on an initramfs image to fail as it might happen that image and initramfs build are called at the same time and the additional image is called before initramfs build has finished. Each image-command assume the source image to be taken from the /bin directory but that is only copied from the /tmp directory only at the end of the process. Artifacts currently depends on image with the use of the BOARD-NAME-images Makefile target, but this is not the case for initramfs that also define a -images Makefile target but that is not accounted in images (that might depend on some initramfs images) To actually fix this, introduce a new Makefile target, -initramfs-images and make image and artifacts build to depend on this. Since initramfs images are optional, this dependency is actived only when initramfs image are built. With this change we correctly enforce the build order: - Initramfs Images (optional) - Images - Artifacts Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* image: respect TARGET_PER_DEVICE_ROOTFS for initramfsLuiz Angelo Daros de Luca2024-07-06
| | | | | | | | | | | | | | | | | | | | | | Initramfs images were using a common rootfs (TARGET_DIR) for all devices, ignoring TARGET_PER_DEVICE_ROOTFS. If a single device required a package to build a functional initramfs image, it should be included by default for all devices or that device should be isolated into a new subtarget. Now the initramfs will be built using the target-specific Implementing Per Device Rootfs for Initramfs is not trivial as the rootfs needs to be embedded in the kernel image. The kernel supports an option to define the initramfs location and the image generation for the kernel can't be run in parallel as other checks are done to config and other arch dependent files. To handle this, we prepare a config for each rootfs and we generate the images under lock to prevent problem with parallel execution. Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com> [ rework implementation for locking support ] Link: https://github.com/openwrt/openwrt/pull/12959 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* build: add APK package build capabilitiesPaul Spooren2024-05-17
| | | | | | | | | A new option called `USE_APK` is added which generated APK packages (.apk) instead of OPKG packages (.ipk). Some features like fstools `snapshot` command are not yet ported Signed-off-by: Paul Spooren <mail@aparcar.org>
* image: add missing DTC include-prefixes directoryÁlvaro Fernández Rojas2024-05-10
| | | | | | | | | include-prefixes were moved to a common directory in linux v4.12, see https://github.com/torvalds/linux/commit/d5d332d3f7e8435e264a71b90178dee69428d630 This is needed for bcm27xx kernel v6.6 support. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* build: also generate the CycloneDX SBOM in imagebuilderFlorian Eckert2024-05-07
| | | | | | | | | | | | | | | | | | The needed file '.packageinfo' for creating the CycloneDX SBOM in the imagebuilder is available in the top directory of the imagebuilder and not in the tmp directory. For this reason, the creation of the CycloneDX SBOM file is not available for the imagebuilder. To fix this, it is now first checked whether the CycloneDX SBOM should be built at all and then second decided by checking the IB variable where the '.packageinfo' file is to be found. With this change, it is now possible to create the CycloneDX SBOM also for the imagebuilder as well. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* treewide: remove implicit SUBTARGETPaul Spooren2024-04-08
| | | | | | | | | | | | | | | | | | Historically it's possible to leave the `SUBTARGETS` undefined and automatically fallback to a "generic" subtarget. This however breaks various downstream scripts which may have expectations around filenames: While some targets with an explicit generic subtarget contain `generic` in the filenames of artifacts, implicit "subtargets" don't. Right now this breaks the CI[1], possibly also scripts using the ImageBuilders. This commit removes all code that support implicit handling of subtargets and instead requires every target to define "SUBTARGETS". [1]: https://github.com/openwrt/openwrt/actions/runs/8592821105/job/23548273630 Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel-build.mk: add support for compiling only DTSChristian Marangi2024-02-08
| | | | | | | | | | | | Add support for compiling DTS for the selected target. This can be useful for testing if the DTS correctly compile and doesn't produce any error. This adds a new make target. To compile only DTS use: make target/linux/dtb Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* image.mk: reorder DTC_WARN_FLAGS based on upstreamRosen Penev2024-01-05
| | | | | | pci warnings got reenabled as they were fixed upstream. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* image: improve UBI image sizing on NAND devicesTony Ambardar2023-11-26
| | | | | | | | | | | | | | | | | | | | | | | | Many NAND devices use a build recipe with "append-ubi | check-size" to ensure factory images don't exceed the target flash partition size. However, UBI reserves space for bad block handling and other operational overhead, and thus 'check-size' can overestimate the space available by several MB. In practice, this means a failed check is definitely a failure, while a passing check is only probably a pass. Improve the situation by teaching 'Build/append-ubi' to check image sizes while accounting for UBI reserved blocks. Add new device variable NAND_SIZE and use with existing IMAGE_SIZE to derate the available space. Each UBI device reserves 20 PEBs per 1024 PEBs of the entire NAND device for bad blocks, plus an additional 4 PEBs overhead. Many devices can transparently enable this check by setting NAND_SIZE based on their flash storage, and may then remove any unneeded 'check-size'. Link: http://www.linux-mtd.infradead.org/doc/ubi.html#L_overhead Suggested-by: Shiji Yang <yangshiji66@qq.com> Suggested-by: Robert Marko <robimarko@gmail.com> Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* image: use helper function for size unitsTony Ambardar2023-11-26
| | | | | | | | Add the make function 'exp_units' for helping evaluate k/m/g size units in expressions, and use this to consistently replace many ad hoc substitutions like '$(subst k,* 1024,$(subst m, * 1024k,$(IMAGE_SIZE)))' in makefiles. Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* treewide: fix shell errors during dump stagePetr Štetiar2023-11-13
| | | | | | | | | | | | | Fixes following issues: bash: -c: line 1: `echo 1686820180<LINUX_VERMAGIC> | /staging_dir/host/bin/mkhash md5 | cut -b1-8' bash: -c: line 1: `echo 1686820180<LINUX_VERMAGIC> | /staging_dir/host/bin/mkhash md5 | sed -E 's/(.{8})(.{4})(.{4})(.{4})(.{10})../\1-\2-\3-\4-\500/'' bash: -c: line 1: syntax error near unexpected token `|' bash: line 1: *1024*1024: syntax error: operand expected (error token is "*1024*1024") bash: line 1: (64 + ): syntax error: operand expected (error token is ")") expr: syntax error: missing argument after '+' Signed-off-by: Petr Štetiar <ynezz@true.cz>
* image: fix image generation within ImageBuilderPetr Štetiar2023-11-06
| | | | | | | | | | | | | | Changes introduced in commit d604a07225c5 ("build: add CycloneDX SBOM JSON support") broke ImageBuilder: Cannot open '/openwrt-imagebuilder-ath79-generic.Linux-x86_64/tmp/.packageinfo': No such file or directory So lets fix it by wrapping the BOM generation behind condition of IB feature check. Fixes: #13881 Fixes: d604a07225c5 ("build: add CycloneDX SBOM JSON support") Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: add CycloneDX SBOM JSON supportPetr Štetiar2023-11-01
| | | | | | | | | | | | | CycloneDX is an open source standard developed by the OWASP foundation. It supports a wide range of development ecosystems, a comprehensive set of use cases, and focuses on automation, ease of adoption, and progressive enhancement of SBOMs (Software Bill Of Materials) throughout build pipelines. So lets add support for CycloneDX SBOM for packages and images manifests. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: add ALT5 vendor/model/variantWenli Looi2023-07-08
| | | | | | This allows adding another device variant. Signed-off-by: Wenli Looi <wlooi@ucalgary.ca>
* image: introduce DEVICE_DTC_FLAGS and DEVICE_DTCO_FLAGSDaniel Golle2023-06-06
| | | | | | | | | | | Handle compiling device tree overlay blobs separate to allow for overlays being compiled with different parameters, mostly to safe space. Allow defining DEVICE_DTC_FLAGS and DEVICE_DTCO_FLAGS as per-device parameters to be passed to dtc. Previously some boards directly used DTC_FLAGS in their build recipe which then also affected other boards. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* image: improve uImage.FIT device tree overlay supportDaniel Golle2023-06-05
| | | | | | | | | | Instead of generating full config nodes incl. kernel, generate minimal config nodes for device tree overlays to be applied to the main config. In this way, multiple device tree overlays can be applied more easily. While at it change filenames to upstream style, ie. use dtso and dtbo suffix for device tree overlays. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* build: Allow specifying uImage timeDavid Yang2023-05-20
| | | | | | | Some U-Boot checks for a specified uImage time and refuses to boot if mismatched. This patch fixes it by recognizing UIMAGE_TIME parameter. Signed-off-by: David Yang <mmyangfl@gmail.com>
* Revert "image: update LZMA_XZ_OPTIONS with new squashfs4 tool"Christian Marangi2023-04-12
| | | | | | | | This reverts commit a33b97dcb1bd6e68f01c571e92ef02c3ab721523. A new version of the squashfs4 tool patch reintroduced the -Xe option. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* image: update LZMA_XZ_OPTIONS with new squashfs4 toolChristian Marangi2023-02-20
| | | | | | | | | The -Xpreset option changed format and dropped the -Xe and just require the extreme string to be passed to the -Xpreset option. Update the LZMA_XZ_OPTIONS to reflect this change. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* build: add ALT3 and ALT4 vendor/model/variantWenli Looi2023-01-25
| | | | | | This is needed for the Netgear EX7300 series v2. Signed-off-by: Wenli Looi <wlooi@ucalgary.ca>
* image: add FACTORY_SIZE to DEFAULT_DEVICE_VARSSander Vanheule2023-01-13
| | | | | | | | | | | | | FACTORY_SIZE is used as a device recipe variable on both the D-Link DIR-825-B1 and Trendnet TEW-673GRU, but is not listed as a device variable, neither globally, nor for ath79. Being assigned the same value, this probably hasn't caused any issues. Add FACTORY_SIZE to the global list DEFAULT_DEVICE_VARS, to ensure the variable is reset for every device, and to allow it to be used outside of the ath79 target. Signed-off-by: Sander Vanheule <sander@svanheule.net>
* image: add gzip-filename build recipeMichael Pratt2023-01-06
| | | | | | | | | | Some vendors use basic gzip metadata (original filename and timestamp) to verify valid images, along with the size of it's contents. Also, add a new device profile variable FACTORY_IMG_NAME which would be ideal to use with this new recipe. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* image: fix device profile specific COMPILE targetsMichael Pratt2022-12-19
| | | | | | | | | | | | | | | Commit a01d23e75 ("image: always rebuild kernel loaders") is a step in the right direction, but exposed some issues and regressions in the makefile. Some of the files made by device specific COMPILE targets start with an "append" command (i.e. >> instead of > redirection) and if the file already exists, the target file is the input to itself before the first recipe-specified input. Fixes: a01d23e75 ("image: always rebuild kernel loaders") Fixes: a7fb589e8 ("image: always rebuild kernel loaders") Signed-off-by: Michael Pratt <mcpratt@pm.me>
* mkits: support definition of DTB loadaddrDavid Bauer2022-11-08
| | | | | | | Support defining a per-device loadaddress for the DTB. This is required for devices which to not align the DTB from the bootloader correctly. Signed-off-by: David Bauer <mail@david-bauer.net>
* image: always rebuild kernel loadersMatthias Schiffer2022-10-14
| | | | | | | | | | | Kernel loaders like the lzma-loader currently don't track changes to their sources. This can lead to an old version of a loader to be used when a build tree is not clean between builds. As the loaders are tiny and the build times are insignificant, simply force rebuilding them on every build to avoid this problem. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* imagebuilder: clean KDIR_TMP before buildingPaul Spooren2022-09-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Building images usally stores them in KDIR_TMP and then copies them over to BIN_DIR. This is fine as rebuilding of images overwrites existing images. When using the EXTRA_IMAGE_NAME variable frequently this fills up the ImageBuilder KDIR_TMP folder since every built image is stored forever. This commit clears the KDIR_TMP folder before building a new image. Below an example how sysupgrade.openwrt.org filled up after the release of 22.03.0 where every created image contains a hash of the package selction in the filename: aparcar@asu-01:~/asu/worker1/cache/22.03.0$ du -d 1 -h 400M ./kirkwood 260M ./gemini 2.0G ./ipq806x 1.7G ./ipq40xx 8.1G ./ramips 4.0K ./octeon 495M ./sunxi 728M ./lantiq 1.8G ./rockchip 3.7G ./mediatek 4.0K ./realtek 5.4G ./mvebu 8.9G ./ath79 3.0G ./bcm47xx 14G ./bcm27xx 11G ./x86 4.0K ./bcm63xx 312M ./mpc85xx 600M ./apm821xx 5.4G ./bcm53xx 66G . Signed-off-by: Paul Spooren <mail@aparcar.org>
* image: drop unused 'BuildKernel/MkFIT'Piotr Dymacz2022-05-12
| | | | | | The 'MkFIT' recipe is no longer used across whole codebase. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* build: store sha256_unsigned in JSONPaul Spooren2022-03-29
| | | | | | | | | | | | Introduce `sha256_unsigned` which is a checksum of the image _before_ a signature is attached. This is helpful to compare image reproducibility. Since the `.sha256sum` file is located in the $(KDIR) folder, switch $(BIN_DIR) with $(KDIR) to simplify the code. The value of $(BIN_DIR) itself is not stored inside the resulting JSON file, so it can be replaced. Signed-off-by: Paul Spooren <mail@aparcar.org>
* image: let mksquashfs4 use all processorsStijn Tintel2022-03-29
| | | | | | | | | | | | | | | | | | | | | | | | | Drop the -processors argument from the mksquashfs4 call, so it will use all available processors. This dramatically reduces the time to create squashfs filesystems. The times below are observed when building an image for my main router, the WatchGuard Firebox M300 (qoriq target): Before: real 4m45,973s After: real 0m23,497s With this commit `mksquashfs` may use more cores than defined via `-j`. This is the same behaviour as for archive creation of ImageBuilder, SDK or toolchain. There is no trivial way to limit `mksquashfs` CPU core usage to the amount of "free" make jobs since two running `mksquashfs` instances would each run with the total allowed number (-j) of threads. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> [extended reasoning in commit message] Signed-off-by: Paul Spooren <mail@aparcar.org>
* build: add support for passing C preprocessor flags for DTS buildsFelix Fietkau2022-03-27
| | | | | | | Useful for adding #ifdefs based on build system provided definitions, or for adding extra include paths Signed-off-by: Felix Fietkau <nbd@nbd.name>
* image: define DEVICE_DTS_DELIMITER as per-device variableChristian Lamparter2021-10-24
| | | | | | | | | DEVICE_DTS_DELIMITER needs to be in the DEFAULT_DEVICE_VARS list to work as expected. This was missing from the original version and got overlooked. Fixes: fd6790864739 ("scripts: mkits.sh: Allow legacy @ mode for dts creation") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* build: store artifacts in JSONPaul Spooren2021-09-14
| | | | | | | | | | | | | Multiple profiles create artifacts, these should be stored in the JSON file as well, allowing downstream tooling to show those files, too. Artifacts don't have specific filesystems so only the fields `name`, `type` and `sha256` are available. Rename env variable names from IMAGE_ to FILE_ prefixes to reflect that images, kernels and artifacts are added with the same command. Signed-off-by: Paul Spooren <mail@aparcar.org>
* image: fix build with SELinuxDaniel Golle2021-08-19
| | | | | | | | The option '-xattr' for mksquashfs4 should be '-xattrs' which lead to build failure with SELinux enabled. Add the missing 's'. Fixes: 4baf47b9a8 ("images: squashfs: xattrs should not depend on buld host") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* images: squashfs: xattrs should not depend on buld hostDaniel Golle2021-08-03
| | | | | | | | | Enable xattr for the generated squashfs only if needed for SELinux. This eliminates warnings during boot on target when building (non-SELinux) OpenWrt on SELinux-enabled hosts like Fedora. Reported-by: fda77 <fda77@users.noreply.github.com> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* build: fix build for devices without initramfsDavid Bauer2021-06-08
| | | | | | | | | Don't attempt to copy initramfs images for devices which do not output an initramfs image. This was breaking builds for mpc85xx-p1010 since mid-march. Signed-off-by: David Bauer <mail@david-bauer.net>
* build/json: fix DEVICE_PACKAGESPaul Spooren2021-06-02
| | | | | | | | | | The variable was missing in the definition of DEFAULT_DEVICE_VARS which caused it to contain wrong values, messing up the resulting JSON files. This patch adds the variable DEVICE_PACKAGES to DEFAULT_DEVICE_VARS. Suggested-by: Baptiste Jonglez <git@bitsofnetworks.org> Signed-off-by: Paul Spooren <mail@aparcar.org>
Powered by cgit, Themed by Ted Yin.