The-Homebrew-Cloud/flashcard-archive
2
0
Fork 0
mirror of https://github.com/DS-Homebrew/flashcard-archive.git synced 2024-11-26 03:24:20 +01:00
Code Issues Packages Projects Releases Wiki Activity
3d1efeb451
flashcard-archive/archive/r4i3d.com/old/Makefile

23 lines
847 B
Makefile
Raw Normal View History

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
Makefile: use $(CURDIR) directly without $(shell pwd) This fixes building on macOS.
2024-10-03 22:52:05 +02:00
export TOPDIR := $(CURDIR)
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
export BASE := r4i3d.com/$(shell basename $(CURDIR))
export OUT := $(TOPDIR)/../../../out
export COMMON := $(TOPDIR)/../../../common-kernels
Bring back the files from the old YSMenu archive
2023-12-27 00:14:25 +01:00
package: directory r4i3d.com_2013_Kernel_1.63.1.zip r4i3d.com_2014-2015_Kernel_1.70.1.zip r4i3d.com_NEW_Kernel_1.38.3.zip R4i3D.com_Kernel_1.4.1M.zip
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
directory:
mkdir -p $(OUT)/$(BASE)
r4i3d.com_2013_Kernel_1.63.1.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)/r4i3d.com_2013_Kernel_1.63.1 && 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
r4i3d.com_2014-2015_Kernel_1.70.1.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)/r4i3d.com_2014-2015_Kernel_1.70.1 && 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
r4i3d.com_NEW_Kernel_1.38.3.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)/r4i3d.com_NEW_Kernel_1.38.3 && zip -r $(OUT)/$(BASE)/$@ *
Bring back the files from the old YSMenu archive
2023-12-27 00:14:25 +01:00
R4i3D.com_Kernel_1.4.1M.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)/R4i3D.com_Kernel_1.4.1M && zip -r $(OUT)/$(BASE)/$@ *
Reference in New Issue Copy Permalink