Raspi-image-spec/Makefile

all: shasums

# List all the supported and built Pi platforms here. They get expanded
# to names like 'raspi_2_buster.yaml' and 'raspi_3_bullseye.img.xz'.
BUILD_FAMILIES := 1 2 3 4
BUILD_RELEASES := buster bullseye

platforms := $(foreach plat, $(BUILD_FAMILIES),$(foreach rel, $(BUILD_RELEASES),  raspi_$(plat)_$(rel)))

shasums: $(addsuffix .sha256,$(platforms)) $(addsuffix .xz.sha256,$(platforms))
xzimages: $(addsuffix .img.xz,$(platforms))
images: $(addsuffix .img,$(platforms))
yaml: $(addsuffix .yaml,$(platforms))

target_platforms:
	@echo $(platforms)

raspi_base_buster.yaml: raspi_master.yaml
	cat raspi_master.yaml | \
	sed "s/__FIRMWARE_PKG__/raspi3-firmware/" | \
	sed "s/__RELEASE__/buster/" > $@

raspi_1_buster.yaml: raspi_base_buster.yaml
	cat raspi_base_buster.yaml | sed "s/__ARCH__/armel/" | \
	sed "s/__LINUX_IMAGE__/linux-image-rpi/" | \
	sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" | \
	sed "s/__DTB__/\\/usr\\/lib\\/linux-image-*-rpi\\/bcm*rpi-*.dtb/" |\
	grep -v "__OTHER_APT_ENABLE__" |\
	sed "s/__HOST__/rpi1/" > $@

raspi_2_buster.yaml: raspi_base_buster.yaml
	cat raspi_base_buster.yaml | sed "s/__ARCH__/armhf/" | \
	sed "s/__LINUX_IMAGE__/linux-image-armmp/" | \
	grep -v "__EXTRA_PKGS__" | \
	sed "s/__DTB__/\\/usr\\/lib\\/linux-image-*-armmp\\/bcm*rpi*.dtb/" |\
	sed "s/__OTHER_APT_ENABLE__//" |\
	sed "s/__HOST__/rpi2/" > $@

raspi_3_buster.yaml: raspi_base_buster.yaml
	cat raspi_base_buster.yaml | sed "s/__ARCH__/arm64/" | \
	sed "s/__LINUX_IMAGE__/linux-image-arm64/" | \
	sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" | \
	sed "s/__DTB__/\\/usr\\/lib\\/linux-image-*-arm64\\/broadcom\\/bcm*rpi*.dtb/" |\
	sed "s/__OTHER_APT_ENABLE__//" |\
	sed "s/__HOST__/rpi3/" > $@

raspi_4_buster.yaml: raspi_base_buster.yaml
	cat raspi_base_buster.yaml | sed "s/__ARCH__/arm64/" | \
	sed "s#raspi3-firmware#raspi-firmware/buster-backports#" | \
	sed "s#apt-get update#echo 'APT::Default-Release \"buster\";' > /etc/apt/apt.conf\n      apt-get update#" | \
	sed "s#cmdline.txt#cmdline.txt\n      sed -i 's/cma=64M //' /boot/firmware/cmdline.txt\n      sed -i 's/cma=\\\$$CMA //' /etc/kernel/postinst.d/z50-raspi-firmware#" | \
	sed "s/__LINUX_IMAGE__/linux-image-arm64\/buster-backports/" | \
	sed "s/__EXTRA_PKGS__/- firmware-brcm80211\/buster-backports/" | \
	sed "s/__DTB__/\\/usr\\/lib\\/linux-image-*-arm64\\/broadcom\\/bcm*rpi*.dtb/" |\
	sed "s/__OTHER_APT_ENABLE__/deb http:\/\/deb.debian.org\/debian\/ buster-backports main contrib non-free # raspi 4 needs a kernel and raspi-firmware newer than buster's/" |\
	sed "s/__HOST__/rpi4/" > $@

raspi_base_bullseye.yaml: raspi_master.yaml
	cat raspi_master.yaml | \
	sed "s/__RELEASE__/bullseye/" |\
	sed "s/__FIRMWARE_PKG__/raspi-firmware/" | \
	grep -v "__OTHER_APT_ENABLE__" |\
	sed -e '/debian-security/ s/deb/# Uncomment after Bullseye becomes stable → deb/' > $@

raspi_1_bullseye.yaml: raspi_base_bullseye.yaml
	cat raspi_base_bullseye.yaml | sed "s/__ARCH__/armel/" | \
	sed "s/__LINUX_IMAGE__/linux-image-rpi/" | \
	sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" | \
	sed "s/__DTB__/\\/usr\\/lib\\/linux-image-*-rpi\\/bcm*rpi-*.dtb/" |\
	sed "s/__HOST__/rpi_1/" > $@

raspi_2_bullseye.yaml: raspi_base_bullseye.yaml
	cat raspi_base_bullseye.yaml | sed "s/__ARCH__/armhf/" | \
	sed "s/__LINUX_IMAGE__/linux-image-armmp/" | \
	grep -v "__EXTRA_PKGS__" | \
	sed "s/__DTB__/\\/usr\\/lib\\/linux-image-*-armmp\\/bcm*rpi*.dtb/" |\
	sed "s/__HOST__/rpi_2/" > $@

raspi_3_bullseye.yaml: raspi_base_bullseye.yaml
	cat raspi_base_bullseye.yaml | sed "s/__ARCH__/arm64/" | \
	sed "s/__LINUX_IMAGE__/linux-image-arm64/" | \
	sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" | \
	sed "s/__DTB__/\\/usr\\/lib\\/linux-image-*-arm64\\/broadcom\\/bcm*rpi*.dtb/" |\
	sed "s/__HOST__/rpi_3/" > $@

raspi_4_bullseye.yaml: raspi_base_bullseye.yaml
	cat raspi_base_bullseye.yaml | sed "s/__ARCH__/arm64/" | \
	sed "s#cmdline.txt#cmdline.txt\n      sed -i 's/cma=64M //' /boot/firmware/cmdline.txt\n      sed -i 's/cma=\\\$$CMA //' /etc/kernel/postinst.d/z50-raspi-firmware#" | \
	sed "s/__LINUX_IMAGE__/linux-image-arm64/" | \
	sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" | \
	sed "s/__DTB__/\\/usr\\/lib\\/linux-image-*-arm64\\/broadcom\\/bcm*rpi*.dtb/" |\
	sed "s/__HOST__/rpi_4/" > $@

%.sha256: %.img.xz
	echo $@
	sha256sum $(@:sha256=img) > $@

%.xz.sha256: %.img.xz
	echo $@
	sha256sum $(@:xz.sha256=img.xz) > $@

%.img.xz: %.img
	xz -f -k -z -9 $(@:.xz=)

%.img: %.yaml
	touch $(@:.img=.log)
	time nice vmdb2 --verbose --rootfs-tarball=$(subst .img,.tar.gz,$@) --output=$@ $(subst .img,.yaml,$@) --log $(subst .img,.log,$@)
	chmod 0644 $@ $(@,.img=.log)

_ck_root:
	[ `whoami` = 'root' ] # Only root can summon vmdb2 ☹

_clean_yaml:
	rm -f $(addsuffix .yaml,$(platforms)) raspi_base_buster.yaml raspi_base_bullseye.yaml
_clean_images:
	rm -f $(addsuffix .img,$(platforms))
_clean_xzimages:
	rm -f $(addsuffix .img.xz,$(platforms))
_clean_shasums:
	rm -f $(addsuffix .sha256,$(platforms)) $(addsuffix .xz.sha256,$(platforms))
_clean_logs:
	rm -f $(addsuffix .log,$(platforms))
_clean_tarballs:
	rm -f $(addsuffix .tar.gz,$(platforms))
clean: _clean_xzimages _clean_images _clean_shasums _clean_yaml _clean_tarballs _clean_logs

.PHONY: _ck_root _build_img clean _clean_images _clean_yaml _clean_tarballs _clean_logs
Some Makefile cleanup; build shasums from the images as well 2020-04-14 19:38:14 +01:00			`all: shasums`

Makefile: use variables for platforms instead of repeating platform numbers Create a variable called BUILD_PLATFORMS that lists the various pi images to build. This keeps the platform list in one place in the makefile, rather than sprinkled and repeated throughout multiple dependency and build lines. When a platform is added (ie, the pi4) or removed, it won't touch multiple rules and obscure other changes. This uses gmake-specific addprefix and addsuffix. 2020-05-04 23:07:01 +01:00			`# List all the supported and built Pi platforms here. They get expanded`
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`# to names like 'raspi_2_buster.yaml' and 'raspi_3_bullseye.img.xz'.`
			`BUILD_FAMILIES := 1 2 3 4`
			`BUILD_RELEASES := buster bullseye`

			`platforms := $(foreach plat, $(BUILD_FAMILIES),$(foreach rel, $(BUILD_RELEASES), raspi_$(plat)_$(rel)))`
Makefile: use variables for platforms instead of repeating platform numbers Create a variable called BUILD_PLATFORMS that lists the various pi images to build. This keeps the platform list in one place in the makefile, rather than sprinkled and repeated throughout multiple dependency and build lines. When a platform is added (ie, the pi4) or removed, it won't touch multiple rules and obscure other changes. This uses gmake-specific addprefix and addsuffix. 2020-05-04 23:07:01 +01:00
			`shasums: $(addsuffix .sha256,$(platforms)) $(addsuffix .xz.sha256,$(platforms))`
			`xzimages: $(addsuffix .img.xz,$(platforms))`
			`images: $(addsuffix .img,$(platforms))`
			`yaml: $(addsuffix .yaml,$(platforms))`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00
Fix missing regex end when calling sed; add target_platforms target 2021-01-26 06:55:23 +00:00			`target_platforms:`
			`@echo $(platforms)`

Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`raspi_base_buster.yaml: raspi_master.yaml`
			`cat raspi_master.yaml \| \`
Fix missing regex end when calling sed; add target_platforms target 2021-01-26 06:55:23 +00:00			`sed "s/__FIRMWARE_PKG__/raspi3-firmware/" \| \`
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`sed "s/__RELEASE__/buster/" > $@`

			`raspi_1_buster.yaml: raspi_base_buster.yaml`
			`cat raspi_base_buster.yaml \| sed "s/__ARCH__/armel/" \| \`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00			`sed "s/__LINUX_IMAGE__/linux-image-rpi/" \| \`
			`sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" \| \`
			`sed "s/__DTB__/\\/usr\\/lib\\/linux-image--rpi\\/bcmrpi-*.dtb/" \|\`
FIX: raspi3-firmware in buster updates now meets requirements 2020-07-06 06:21:19 +01:00			`grep -v "__OTHER_APT_ENABLE__" \|\`
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`sed "s/__HOST__/rpi1/" > $@`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`raspi_2_buster.yaml: raspi_base_buster.yaml`
			`cat raspi_base_buster.yaml \| sed "s/__ARCH__/armhf/" \| \`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00			`sed "s/__LINUX_IMAGE__/linux-image-armmp/" \| \`
			`grep -v "__EXTRA_PKGS__" \| \`
			`sed "s/__DTB__/\\/usr\\/lib\\/linux-image--armmp\\/bcmrpi*.dtb/" \|\`
non-free must be enabled for updated raspi3-firmware on armel to be pulled in :-Þ 2020-04-24 17:00:10 +01:00			`sed "s/__OTHER_APT_ENABLE__//" \|\`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00			`sed "s/__HOST__/rpi2/" > $@`

Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`raspi_3_buster.yaml: raspi_base_buster.yaml`
			`cat raspi_base_buster.yaml \| sed "s/__ARCH__/arm64/" \| \`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00			`sed "s/__LINUX_IMAGE__/linux-image-arm64/" \| \`
			`sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" \| \`
			`sed "s/__DTB__/\\/usr\\/lib\\/linux-image--arm64\\/broadcom\\/bcmrpi*.dtb/" \|\`
non-free must be enabled for updated raspi3-firmware on armel to be pulled in :-Þ 2020-04-24 17:00:10 +01:00			`sed "s/__OTHER_APT_ENABLE__//" \|\`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00			`sed "s/__HOST__/rpi3/" > $@`

Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`raspi_4_buster.yaml: raspi_base_buster.yaml`
			`cat raspi_base_buster.yaml \| sed "s/__ARCH__/arm64/" \| \`
All packages needed for RPi4 are now in buster/backports, stop bringing unstable in 2020-11-05 17:35:58 +00:00			`sed "s#raspi3-firmware#raspi-firmware/buster-backports#" \| \`
Use "buster" instead of "stable" for the RPi4 default apt release (Salsa issue #30) 2020-10-16 16:49:18 +01:00			`sed "s#apt-get update#echo 'APT::Default-Release \"buster\";' > /etc/apt/apt.conf\n apt-get update#" \| \`
Generate a raspi_4.yaml This allows you to run "make raspi_4.img" and create a raspberry pi 4 image. It doesn't yet add pi 4 to the list of images that are autobuilt. We're pulling the latest kernel and raspi3-firmware in order to get pi4 support (which was added in Linux 5.5). We're also working around a bug where cma= stops the 5.6 kernel from booting (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951744#10). This is based on Lucas Nussbaum's initial yaml. 2020-05-11 00:53:22 +01:00			`sed "s#cmdline.txt#cmdline.txt\n sed -i 's/cma=64M //' /boot/firmware/cmdline.txt\n sed -i 's/cma=\\\$$CMA //' /etc/kernel/postinst.d/z50-raspi-firmware#" \| \`
All packages needed for RPi4 are now in buster/backports, stop bringing unstable in 2020-11-05 17:35:58 +00:00			`sed "s/__LINUX_IMAGE__/linux-image-arm64\/buster-backports/" \| \`
			`sed "s/__EXTRA_PKGS__/- firmware-brcm80211\/buster-backports/" \| \`
Generate a raspi_4.yaml This allows you to run "make raspi_4.img" and create a raspberry pi 4 image. It doesn't yet add pi 4 to the list of images that are autobuilt. We're pulling the latest kernel and raspi3-firmware in order to get pi4 support (which was added in Linux 5.5). We're also working around a bug where cma= stops the 5.6 kernel from booting (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951744#10). This is based on Lucas Nussbaum's initial yaml. 2020-05-11 00:53:22 +01:00			`sed "s/__DTB__/\\/usr\\/lib\\/linux-image--arm64\\/broadcom\\/bcmrpi*.dtb/" \|\`
All packages needed for RPi4 are now in buster/backports, stop bringing unstable in 2020-11-05 17:35:58 +00:00			`sed "s/__OTHER_APT_ENABLE__/deb http:\/\/deb.debian.org\/debian\/ buster-backports main contrib non-free # raspi 4 needs a kernel and raspi-firmware newer than buster's/" \|\`
Generate a raspi_4.yaml This allows you to run "make raspi_4.img" and create a raspberry pi 4 image. It doesn't yet add pi 4 to the list of images that are autobuilt. We're pulling the latest kernel and raspi3-firmware in order to get pi4 support (which was added in Linux 5.5). We're also working around a bug where cma= stops the 5.6 kernel from booting (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951744#10). This is based on Lucas Nussbaum's initial yaml. 2020-05-11 00:53:22 +01:00			`sed "s/__HOST__/rpi4/" > $@`

Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`raspi_base_bullseye.yaml: raspi_master.yaml`
			`cat raspi_master.yaml \| \`
			`sed "s/__RELEASE__/bullseye/" \|\`
Don't use the transition firmware package when building for bullseye 2021-01-25 20:27:26 +00:00			`sed "s/__FIRMWARE_PKG__/raspi-firmware/" \| \`
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`grep -v "__OTHER_APT_ENABLE__" \|\`
			`sed -e '/debian-security/ s/deb/# Uncomment after Bullseye becomes stable → deb/' > $@`

			`raspi_1_bullseye.yaml: raspi_base_bullseye.yaml`
			`cat raspi_base_bullseye.yaml \| sed "s/__ARCH__/armel/" \| \`
Enable the build of Bullseye targets as well 2021-01-14 06:55:55 +00:00			`sed "s/__LINUX_IMAGE__/linux-image-rpi/" \| \`
			`sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" \| \`
			`sed "s/__DTB__/\\/usr\\/lib\\/linux-image--rpi\\/bcmrpi-*.dtb/" \|\`
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`sed "s/__HOST__/rpi_1/" > $@`
Enable the build of Bullseye targets as well 2021-01-14 06:55:55 +00:00
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`raspi_2_bullseye.yaml: raspi_base_bullseye.yaml`
			`cat raspi_base_bullseye.yaml \| sed "s/__ARCH__/armhf/" \| \`
Enable the build of Bullseye targets as well 2021-01-14 06:55:55 +00:00			`sed "s/__LINUX_IMAGE__/linux-image-armmp/" \| \`
			`grep -v "__EXTRA_PKGS__" \| \`
			`sed "s/__DTB__/\\/usr\\/lib\\/linux-image--armmp\\/bcmrpi*.dtb/" \|\`
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`sed "s/__HOST__/rpi_2/" > $@`
Enable the build of Bullseye targets as well 2021-01-14 06:55:55 +00:00
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`raspi_3_bullseye.yaml: raspi_base_bullseye.yaml`
			`cat raspi_base_bullseye.yaml \| sed "s/__ARCH__/arm64/" \| \`
Enable the build of Bullseye targets as well 2021-01-14 06:55:55 +00:00			`sed "s/__LINUX_IMAGE__/linux-image-arm64/" \| \`
			`sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" \| \`
			`sed "s/__DTB__/\\/usr\\/lib\\/linux-image--arm64\\/broadcom\\/bcmrpi*.dtb/" \|\`
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`sed "s/__HOST__/rpi_3/" > $@`

			`raspi_4_bullseye.yaml: raspi_base_bullseye.yaml`
			`cat raspi_base_bullseye.yaml \| sed "s/__ARCH__/arm64/" \| \`
			`sed "s#cmdline.txt#cmdline.txt\n sed -i 's/cma=64M //' /boot/firmware/cmdline.txt\n sed -i 's/cma=\\\$$CMA //' /etc/kernel/postinst.d/z50-raspi-firmware#" \| \`
			`sed "s/__LINUX_IMAGE__/linux-image-arm64/" \| \`
			`sed "s/__EXTRA_PKGS__/- firmware-brcm80211/" \| \`
			`sed "s/__DTB__/\\/usr\\/lib\\/linux-image--arm64\\/broadcom\\/bcmrpi*.dtb/" \|\`
			`sed "s/__HOST__/rpi_4/" > $@`
Enable the build of Bullseye targets as well 2021-01-14 06:55:55 +00:00
Add xzimages target; build shasums based on them instead 2020-04-15 04:27:20 +01:00			`%.sha256: %.img.xz`
Generate shasums for images both compressed and uncompressed 2020-04-27 17:59:56 +01:00			`echo $@`
			`sha256sum $(@:sha256=img) > $@`

			`%.xz.sha256: %.img.xz`
			`echo $@`
			`sha256sum $(@:xz.sha256=img.xz) > $@`
Add xzimages target; build shasums based on them instead 2020-04-15 04:27:20 +01:00
			`%.img.xz: %.img`
Added xzimages to clean target; keep images when preparing xzimages 2020-04-24 16:37:52 +01:00			`xz -f -k -z -9 $(@:.xz=)`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00
Some Makefile cleanup; build shasums from the images as well 2020-04-14 19:38:14 +01:00			`%.img: %.yaml`
			`touch $(@:.img=.log)`
			`time nice vmdb2 --verbose --rootfs-tarball=$(subst .img,.tar.gz,$@) --output=$@ $(subst .img,.yaml,$@) --log $(subst .img,.log,$@)`
			`chmod 0644 $@ $(@,.img=.log)`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00
			`_ck_root:`
			[ `whoami` = 'root' ] # Only root can summon vmdb2 ☹

			`_clean_yaml:`
Use a more coherent, stable naming for build families and releases 2021-01-25 20:06:46 +00:00			`rm -f $(addsuffix .yaml,$(platforms)) raspi_base_buster.yaml raspi_base_bullseye.yaml`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00			`_clean_images:`
Makefile: use variables for platforms instead of repeating platform numbers Create a variable called BUILD_PLATFORMS that lists the various pi images to build. This keeps the platform list in one place in the makefile, rather than sprinkled and repeated throughout multiple dependency and build lines. When a platform is added (ie, the pi4) or removed, it won't touch multiple rules and obscure other changes. This uses gmake-specific addprefix and addsuffix. 2020-05-04 23:07:01 +01:00			`rm -f $(addsuffix .img,$(platforms))`
Added xzimages to clean target; keep images when preparing xzimages 2020-04-24 16:37:52 +01:00			`_clean_xzimages:`
Makefile: use variables for platforms instead of repeating platform numbers Create a variable called BUILD_PLATFORMS that lists the various pi images to build. This keeps the platform list in one place in the makefile, rather than sprinkled and repeated throughout multiple dependency and build lines. When a platform is added (ie, the pi4) or removed, it won't touch multiple rules and obscure other changes. This uses gmake-specific addprefix and addsuffix. 2020-05-04 23:07:01 +01:00			`rm -f $(addsuffix .img.xz,$(platforms))`
Some Makefile cleanup; build shasums from the images as well 2020-04-14 19:38:14 +01:00			`_clean_shasums:`
Makefile: use variables for platforms instead of repeating platform numbers Create a variable called BUILD_PLATFORMS that lists the various pi images to build. This keeps the platform list in one place in the makefile, rather than sprinkled and repeated throughout multiple dependency and build lines. When a platform is added (ie, the pi4) or removed, it won't touch multiple rules and obscure other changes. This uses gmake-specific addprefix and addsuffix. 2020-05-04 23:07:01 +01:00			`rm -f $(addsuffix .sha256,$(platforms)) $(addsuffix .xz.sha256,$(platforms))`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00			`_clean_logs:`
Makefile: use variables for platforms instead of repeating platform numbers Create a variable called BUILD_PLATFORMS that lists the various pi images to build. This keeps the platform list in one place in the makefile, rather than sprinkled and repeated throughout multiple dependency and build lines. When a platform is added (ie, the pi4) or removed, it won't touch multiple rules and obscure other changes. This uses gmake-specific addprefix and addsuffix. 2020-05-04 23:07:01 +01:00			`rm -f $(addsuffix .log,$(platforms))`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00			`_clean_tarballs:`
Makefile: use variables for platforms instead of repeating platform numbers Create a variable called BUILD_PLATFORMS that lists the various pi images to build. This keeps the platform list in one place in the makefile, rather than sprinkled and repeated throughout multiple dependency and build lines. When a platform is added (ie, the pi4) or removed, it won't touch multiple rules and obscure other changes. This uses gmake-specific addprefix and addsuffix. 2020-05-04 23:07:01 +01:00			`rm -f $(addsuffix .tar.gz,$(platforms))`
Added xzimages to clean target; keep images when preparing xzimages 2020-04-24 16:37:52 +01:00			`clean: _clean_xzimages _clean_images _clean_shasums _clean_yaml _clean_tarballs _clean_logs`
Added a Makefile driving a raspi_master recipe This is instead of maintaining separate recipes for 0w, 2 and 3 hardware 2019-12-17 20:41:16 +00:00
			`.PHONY: _ck_root _build_img clean _clean_images _clean_yaml _clean_tarballs _clean_logs`