aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/kirkwood
diff options
context:
space:
mode:
authorPetr Štetiar <ynezz@true.cz>2018-11-23 10:53:37 +0100
committerJo-Philipp Wich <jo@mein.io>2018-12-18 17:22:03 +0100
commit9885d3aec1db0830a1df98da9793d9506b0cbc58 (patch)
tree880944d2e0402b6c1a826e692993a10c6cba1797 /target/linux/kirkwood
parent16f4057188b7fd4bc8126600d053a1822231cc36 (diff)
downloadupstream-9885d3aec1db0830a1df98da9793d9506b0cbc58.tar.gz
upstream-9885d3aec1db0830a1df98da9793d9506b0cbc58.tar.bz2
upstream-9885d3aec1db0830a1df98da9793d9506b0cbc58.zip
build: Introduce building of artifacts
We currently could (ab)use IMAGES for this task, but the downside is, that the filenames has filesystem tied to the filename, which might be confusing as the artifact itself don't has to be used with that specific filesystem. Another downside is, that the artifacts built with IMAGES target are build for every FILESYSTEMS filesystem. Consider following use case: define Device/apalis ... FILESYSTEMS := ext4 squashfs IMAGES := spl-uboot.bin recovery.scr IMAGE/spl-uboot.bin := append-uboot-spl | pad-to 68k | append-uboot IMAGE/recovery.scr := recovery-scr endef Where we would get target binaries with following filenames: openwrt-imx6-apalis-squashfs.recovery.scr openwrt-imx6-apalis-squashfs.spl-uboot.bin openwrt-imx6-apalis-ext4.recovery.scr openwrt-imx6-apalis-ext4.spl-uboot.bin With proposed patch, we could now just do: define Device/apalis ... ARTIFACTS := spl-uboot.bin recovery.scr ARTIFACT/spl-uboot.bin := append-uboot-spl | pad-to 68k | append-uboot ARTIFACT/recovery.scr := recovery-scr endef Which would produce target binaries with following filenames: openwrt-imx6-apalis-recovery.scr openwrt-imx6-apalis-spl-uboot.bin Signed-off-by: Petr Štetiar <ynezz@true.cz> Acked-by: Hauke Mehrtens <hauke@hauke-m.de> (backported from 493c9a35516c27a8ec412d97e63c8cf6f41a57ea)
Diffstat (limited to 'target/linux/kirkwood')
0 files changed, 0 insertions, 0 deletions