Hibbian
/
Raspi-image-spec
1
0
Fork 0
Code Issues 3 Pull Requests Packages Projects Releases Wiki Activity
Raspi-image-spec/Makefile

76 lines
2.4 KiB
Makefile
Raw Normal View History

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
Add basic support for trixie. In passing: the _clean_yaml target should definitely leverage BUILD_RELEASES instead of duplicating it.
2023-06-13 20:02:39 +01:00
BUILD_RELEASES := buster bullseye bookworm trixie
Use a more coherent, stable naming for build families and releases
2021-01-25 20:06:46 +00:00
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
Fix generated suffix for .img.sha256 files
2021-08-24 19:22:36 +01:00
shasums: $(addsuffix .img.sha256,$(platforms)) $(addsuffix .img.xz.sha256,$(platforms))
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
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
Makefile: Automatically use fakemachine if not uid 0 fakemachine launches a virtual machine reusing the host system's /usr, and runs commands as root on that virtual machine. It's used by debos, but can also be used to wrap arbitrary commands, in particular vmdb2; it's enough to run the parts of vmdb2 that need to mount filesystems and run apt. This won't work if fakemachine isn't available (in particular on non-x86), but that seems better than just failing altogether. Signed-off-by: Simon McVittie <smcv@debian.org>
2021-04-24 23:07:01 +01:00
ifeq ($(shell id -u),0)
as_root =
Add check whether 'fakemachine' exists. Give a warning message if it does and an error when it does not. Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
2021-06-24 19:22:55 +01:00
else ifneq (,$(wildcard /usr/bin/fakemachine))
$(warning "This should normally be run as root, but found 'fakemachine', so using that.")
Makefile: Automatically use fakemachine if not uid 0 fakemachine launches a virtual machine reusing the host system's /usr, and runs commands as root on that virtual machine. It's used by debos, but can also be used to wrap arbitrary commands, in particular vmdb2; it's enough to run the parts of vmdb2 that need to mount filesystems and run apt. This won't work if fakemachine isn't available (in particular on non-x86), but that seems better than just failing altogether. Signed-off-by: Simon McVittie <smcv@debian.org>
2021-04-24 23:07:01 +01:00
as_root = fakemachine -v $(CURDIR) -- env --chdir $(CURDIR)
Add check whether 'fakemachine' exists. Give a warning message if it does and an error when it does not. Signed-off-by: Diederik de Haas <didi.debian@cknow.org>
2021-06-24 19:22:55 +01:00
else
$(error "This must be run as root")
Makefile: Automatically use fakemachine if not uid 0 fakemachine launches a virtual machine reusing the host system's /usr, and runs commands as root on that virtual machine. It's used by debos, but can also be used to wrap arbitrary commands, in particular vmdb2; it's enough to run the parts of vmdb2 that need to mount filesystems and run apt. This won't work if fakemachine isn't available (in particular on non-x86), but that seems better than just failing altogether. Signed-off-by: Simon McVittie <smcv@debian.org>
2021-04-24 23:07:01 +01:00
endif
Fix missing regex end when calling sed; add target_platforms target
2021-01-26 06:55:23 +00:00
target_platforms:
@echo $(platforms)
Replace the sed maze with one generate-recipe call for each combination.
2021-08-28 04:51:05 +01:00
# Generate targets based on all family * release combinations:
define dynamic_yaml_target =
raspi_$(1)_$(2).yaml: raspi_master.yaml generate-recipe.py
raspi_$(1)_$(2).yaml:
./generate-recipe.py $(1) $(2)
endef
Improve loop readability. Split dynamic target generation across several lines to make the nested loops more obvious. Backslashes are needed for make to be happy about what would otherwise be detected as unfinished foreach function calls.
2021-08-28 04:52:51 +01:00
$(foreach release,$(BUILD_RELEASES), \
$(foreach family,$(BUILD_FAMILIES), \
$(eval $(call dynamic_yaml_target,$(family),$(release)))))
Enable the build of Bullseye targets as well
2021-01-14 06:55:55 +00:00
Fix shasums target. Without this, a plain `make` would result in: make: *** No rule to make target 'raspi_1_buster.img.sha256', needed by 'shasums'. Stop.
2021-08-28 05:00:09 +01:00
%.img.sha256: %.img
Generate shasums for images both compressed and uncompressed
2020-04-27 17:59:56 +01:00
echo $@
Use the $< automatic variable. That's the name of the first prerequisite.
2021-08-28 05:02:43 +01:00
sha256sum $< > $@
Generate shasums for images both compressed and uncompressed
2020-04-27 17:59:56 +01:00
Shasums for the compressed images should use consistent naming -- generate them as .img.xz.sha256
2021-08-23 17:58:32 +01:00
%.img.xz.sha256: %.img.xz
Generate shasums for images both compressed and uncompressed
2020-04-27 17:59:56 +01:00
echo $@
Use the $< automatic variable. That's the name of the first prerequisite.
2021-08-28 05:02:43 +01:00
sha256sum $< > $@
Add xzimages target; build shasums based on them instead
2020-04-15 04:27:20 +01:00
%.img.xz: %.img
Use the $< automatic variable. That's the name of the first prerequisite.
2021-08-28 05:02:43 +01:00
xz -f -k -z -9 $<
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
Makefile: Optionally generate a bmaptool map file bmaptool(1), from the bmap-tools package, can write the used blocks in a sparse disk image to media, while saving time and I/O by not writing zeroes to the unused blocks. Typical use: make raspi2_bullseye.img.bmap raspi2_bullseye.img.xz ... upload those two files ... ... download those two files ... bmaptool copy raspi2_bullseye.img.xz /dev/disk/by-id/usb-Generic-_SD_MMC_*-0:0 Signed-off-by: Simon McVittie <smcv@debian.org>
2021-04-24 23:20:12 +01:00
%.img.bmap: %.img
bmaptool create -o $@ $<
Some Makefile cleanup; build shasums from the images as well
2020-04-14 19:38:14 +01:00
%.img: %.yaml
touch $(@:.img=.log)
Makefile: Automatically use fakemachine if not uid 0 fakemachine launches a virtual machine reusing the host system's /usr, and runs commands as root on that virtual machine. It's used by debos, but can also be used to wrap arbitrary commands, in particular vmdb2; it's enough to run the parts of vmdb2 that need to mount filesystems and run apt. This won't work if fakemachine isn't available (in particular on non-x86), but that seems better than just failing altogether. Signed-off-by: Simon McVittie <smcv@debian.org>
2021-04-24 23:07:01 +01:00
time nice $(as_root) vmdb2 --verbose --rootfs-tarball=$(subst .img,.tar.gz,$@) --output=$@ $(subst .img,.yaml,$@) --log $(subst .img,.log,$@)
Some Makefile cleanup; build shasums from the images as well
2020-04-14 19:38:14 +01:00
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:
Add basic support for trixie. In passing: the _clean_yaml target should definitely leverage BUILD_RELEASES instead of duplicating it.
2023-06-13 20:02:39 +01:00
rm -f $(addsuffix .yaml,$(platforms)) raspi_base_buster.yaml raspi_base_bullseye.yaml raspi_base_bookworm.yaml raspi_base_trixie.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))
Makefile: Optionally generate a bmaptool map file bmaptool(1), from the bmap-tools package, can write the used blocks in a sparse disk image to media, while saving time and I/O by not writing zeroes to the unused blocks. Typical use: make raspi2_bullseye.img.bmap raspi2_bullseye.img.xz ... upload those two files ... ... download those two files ... bmaptool copy raspi2_bullseye.img.xz /dev/disk/by-id/usb-Generic-_SD_MMC_*-0:0 Signed-off-by: Simon McVittie <smcv@debian.org>
2021-04-24 23:20:12 +01:00
_clean_bmaps:
rm -f $(addsuffix .img.bmap,$(platforms))
Some Makefile cleanup; build shasums from the images as well
2020-04-14 19:38:14 +01:00
_clean_shasums:
Fix _clean_shasums to also remove *.img.sha256. Commit 422a0d60 fixed the img.sha256 target itself, but it didn't update the corresponding clean variant, so add that too. Signed-off-by: Diederik de Haas <didi.debian@cknow.org> (cherry picked from commit 60513d46f6f687a2582be3b9a9589ea6259813b9) Signed-off-by: Cyril Brulebois <cyril@debamax.com>
2021-09-09 00:00:59 +01:00
rm -f $(addsuffix .img.sha256,$(platforms)) $(addsuffix .img.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))
Makefile: Optionally generate a bmaptool map file bmaptool(1), from the bmap-tools package, can write the used blocks in a sparse disk image to media, while saving time and I/O by not writing zeroes to the unused blocks. Typical use: make raspi2_bullseye.img.bmap raspi2_bullseye.img.xz ... upload those two files ... ... download those two files ... bmaptool copy raspi2_bullseye.img.xz /dev/disk/by-id/usb-Generic-_SD_MMC_*-0:0 Signed-off-by: Simon McVittie <smcv@debian.org>
2021-04-24 23:20:12 +01:00
clean: _clean_xzimages _clean_images _clean_shasums _clean_yaml _clean_tarballs _clean_logs _clean_bmaps
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