Raspi-image-spec/Makefile

all: shasums

# List all the supported and built Pi platforms here. They get expanded
# to names like 'raspi_2.yaml' and 'raspi_0w.img.xz'.
BUILD_PLATFORMS := 0w 2 3

platforms := $(addprefix raspi_,$(BUILD_PLATFORMS))
shasums: $(addsuffix .sha256,$(platforms)) $(addsuffix .xz.sha256,$(platforms))
xzimages: $(addsuffix .img.xz,$(platforms))
images: $(addsuffix .img,$(platforms))
yaml: $(addsuffix .yaml,$(platforms))

raspi_0w.yaml: raspi_master.yaml
	cat raspi_master.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/__OTHER_APT_ENABLE__/deb http:\/\/deb.debian.org\/debian\/ buster-proposed-updates main contrib non-free # Raspberries 0\/1 need raspi3-firmware >=  1.20190215-1+deb10u3/" |\
	sed "s/__HOST__/rpi0/" > $@

raspi_2.yaml: raspi_master.yaml
	cat raspi_master.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.yaml: raspi_master.yaml
	cat raspi_master.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/" > $@

%.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))
_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`
			`# to names like 'raspi_2.yaml' and 'raspi_0w.img.xz'.`
			`BUILD_PLATFORMS := 0w 2 3`

			`platforms := $(addprefix raspi_,$(BUILD_PLATFORMS))`
			`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
			`raspi_0w.yaml: raspi_master.yaml`
			`cat raspi_master.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\\/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__/deb http:\/\/deb.debian.org\/debian\/ buster-proposed-updates main contrib non-free # Raspberries 0\/1 need raspi3-firmware >= 1.20190215-1+deb10u3/" \|\`
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__/rpi0/" > $@`

			`raspi_2.yaml: raspi_master.yaml`
			`cat raspi_master.yaml \| sed "s/__ARCH__/armhf/" \| \`
			`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/" > $@`

			`raspi_3.yaml: raspi_master.yaml`
			`cat raspi_master.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\\/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/" > $@`

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:`
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 .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			`_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`