flashcard-archive/archive/pandora-ds.com/Makefile

.PHONY: package

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

package: directory pandora-ds.com_Kernel.zip

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

pandora-ds.com_Kernel.zip: directory
	cd $(TOPDIR)/pandora-ds.com_Kernel && zip -r $(OUT)/$(BASE)/$@ *
Add Makefile system to create frontend Run `./build.sh` in `archive` folder. It will loop through all kernels, and copy to `<project-root>/out`. 2023-08-13 18:46:40 +02:00			`.PHONY: package`

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

			`package: directory pandora-ds.com_Kernel.zip`

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

			`pandora-ds.com_Kernel.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-15 06:59:35 +01:00			`cd $(TOPDIR)/pandora-ds.com_Kernel && zip -r $(OUT)/$(BASE)/$@ *`