collapseos/recipes/rc2014/Makefile

TARGET = os.bin
ZASM = ../../tools/zasm.sh
KERNEL = ../../kernel
APPS = ../../apps

.PHONY: all
all: $(TARGET)
$(TARGET): glue.asm
	$(ZASM) $(KERNEL) $(APPS) < $< > $@
Split parts in two: z80 and avr Also, clarify the role of recipes. 2019-04-26 06:03:45 +10:00			`TARGET = os.bin`
Parametrize zasm linux bin's include CFS file ... instead of embedding it in the binary itself. Additionally, add a "zasm.sh" wrapper to faciliate zasm calls on a linux machine. 2019-06-03 05:50:59 +10:00			`ZASM = ../../tools/zasm.sh`
zasm: includes CFS is now built on-the-fly by zasm.sh This makes for a much more usable zasm linux binary that doesn't have to be rebuilt every time apps or kernel change. 2019-06-03 09:54:37 +10:00			`KERNEL = ../../kernel`
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer. 2019-11-16 07:37:49 +11:00			`APPS = ../../apps`
Split parts in two: z80 and avr Also, clarify the role of recipes. 2019-04-26 06:03:45 +10:00
			`.PHONY: all`
			`all: $(TARGET)`
			`$(TARGET): glue.asm`
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer. 2019-11-16 07:37:49 +11:00			`$(ZASM) $(KERNEL) $(APPS) < $< > $@`