flashcard-archive/archive/iPlayer/Makefile

.PHONY: package

export TOPDIR := $(shell pwd $(CURDIR))
export BASE   := $(shell basename $(CURDIR))
export OUT    := $(TOPDIR)/../../out
export COMMON := $(TOPDIR)/../../common-kernels

package: directory iPlayer_OS_1.3-20120323.zip

directory:
	mkdir -p $(OUT)/$(BASE)

iPlayer_OS_1.3-20120323.zip: directory
	cd $(TOPDIR)/iPlayer_OS_1.3-20120323 && zip -r $(OUT)/$(BASE)/$@ *
Add iPlayer kernel and latest firmware 2023-08-15 06:38:39 -07:00			`.PHONY: package`

			`export TOPDIR := $(shell pwd $(CURDIR))`
			`export BASE := $(shell basename $(CURDIR))`
			`export OUT := $(TOPDIR)/../../out`
			`export COMMON := $(TOPDIR)/../../common-kernels`

iPlayer: fix missing README 2024-08-21 21:21:48 -07:00			`package: directory iPlayer_OS_1.3-20120323.zip`
Add iPlayer kernel and latest firmware 2023-08-15 06:38:39 -07:00
			`directory:`
			`mkdir -p $(OUT)/$(BASE)`

			`iPlayer_OS_1.3-20120323.zip: directory`
treewide: use deterministic-zip https://github.com/timo-reymann/deterministic-zip This solves a logistics issue; zip files always include the modified timestamp of a file. This doesn't sound bad until you realize that GitHub Actions always re-clones the entire repository, and the timestamp is guaranteed to be different. Because of this, every time we run our Actions workflow, the zip will have a different checksum, causing git to re-commit every single file to the frontend repository, causing long workflow times due to the sheer size of each commit. deterministic-zip hopefully solves this issue by forcing the modified timestamp to one hardcoded in its binary, so here is to hoping we don't abuse our git repo any further. 2024-01-14 21:59:35 -08:00			`cd $(TOPDIR)/iPlayer_OS_1.3-20120323 && zip -r $(OUT)/$(BASE)/$@ *`