collapseos/tools/emul/Makefile

TARGETS = shell/shell zasm/zasm
KERNEL_HEADERS = shell/kernel.h zasm/kernel.h
USER_HEADERS = zasm/user.h
CFSPACK = ../cfspack/cfspack

.PHONY: all
all: $(TARGETS)

shell/kernel.h: shell/shell_.asm
zasm/kernel.h: zasm/glue.asm
$(KERNEL_HEADERS):
	scas -o - -I ../../parts/z80 $< | ./bin2c.sh KERNEL | tee $@ > /dev/null

zasm/user.h: zasm/user.asm
	scas -o - -I ../../apps/zasm $< | ./bin2c.sh USERSPACE | tee $@ > /dev/null

zasm/includes.cfs: ../../parts/z80 $(CFSPACK)
	cp -rf $< zasm/includes
	rm zasm/includes/README.md
	$(CFSPACK) zasm/includes > $@
	rm -rf zasm/includes

zasm/includes.h: zasm/includes.cfs
	./bin2c.sh FSDEV < $< | tee $@ > /dev/null
	
shell/shell: shell/shell.c libz80/libz80.o shell/kernel.h $(CFSPACK)
zasm/zasm: zasm/zasm.c libz80/libz80.o zasm/kernel.h zasm/user.h zasm/includes.h
$(TARGETS):
	cc $< libz80/libz80.o -o $@

libz80/libz80.o: libz80/z80.c
	make -C libz80/codegen opcodes
	gcc -Wall -ansi -g -c -o libz80/libz80.o libz80/z80.c

$(CFSPACK):
	make -C ../cfspack

.PHONY: clean
clean:
	rm -f $(TARGETS) $(KERNEL_HEADERS) $(USER_HEADERS) zasm/includes.*
tools/emul: clean up the place a bit 2019-05-17 07:23:59 -04:00			`TARGETS = shell/shell zasm/zasm`
			`KERNEL_HEADERS = shell/kernel.h zasm/kernel.h`
			`USER_HEADERS = zasm/user.h`
zasm emul: add tooling for includes fsdev On build, pack `parts/z80` into a CFS and embed it into the emulated zasm executable as an fsdev. This will allow for the upcoming include directive to have something to go to. For now, this is useless except for inflating the emulated zasm's size. 2019-05-16 12:07:57 -04:00			`CFSPACK = ../cfspack/cfspack`
Move apps/zasm/emul to tools/emul 2019-05-09 14:09:40 -04:00
Add tools/emul 2019-05-09 12:58:41 -04:00			`.PHONY: all`
Move apps/zasm/emul to tools/emul 2019-05-09 14:09:40 -04:00			`all: $(TARGETS)`
Add tools/emul 2019-05-09 12:58:41 -04:00
tools/emul: clean up the place a bit 2019-05-17 07:23:59 -04:00			`shell/kernel.h: shell/shell_.asm`
			`zasm/kernel.h: zasm/glue.asm`
Move apps/zasm/emul to tools/emul 2019-05-09 14:09:40 -04:00			`$(KERNEL_HEADERS):`
			`scas -o - -I ../../parts/z80 $< \| ./bin2c.sh KERNEL \| tee $@ > /dev/null`

tools/emul: clean up the place a bit 2019-05-17 07:23:59 -04:00			`zasm/user.h: zasm/user.asm`
Move apps/zasm/emul to tools/emul 2019-05-09 14:09:40 -04:00			`scas -o - -I ../../apps/zasm $< \| ./bin2c.sh USERSPACE \| tee $@ > /dev/null`
Add tools/emul 2019-05-09 12:58:41 -04:00
tools/emul: clean up the place a bit 2019-05-17 07:23:59 -04:00			`zasm/includes.cfs: ../../parts/z80 $(CFSPACK)`
			`cp -rf $< zasm/includes`
			`rm zasm/includes/README.md`
			`$(CFSPACK) zasm/includes > $@`
			`rm -rf zasm/includes`
zasm emul: add tooling for includes fsdev On build, pack `parts/z80` into a CFS and embed it into the emulated zasm executable as an fsdev. This will allow for the upcoming include directive to have something to go to. For now, this is useless except for inflating the emulated zasm's size. 2019-05-16 12:07:57 -04:00
tools/emul: clean up the place a bit 2019-05-17 07:23:59 -04:00			`zasm/includes.h: zasm/includes.cfs`
zasm: iiiiiiiincluuuuuuudes!!1! 2019-05-16 21:15:00 -04:00			`./bin2c.sh FSDEV < $< \| tee $@ > /dev/null`

tools/emul: clean up the place a bit 2019-05-17 07:23:59 -04:00			`shell/shell: shell/shell.c libz80/libz80.o shell/kernel.h $(CFSPACK)`
			`zasm/zasm: zasm/zasm.c libz80/libz80.o zasm/kernel.h zasm/user.h zasm/includes.h`
Move apps/zasm/emul to tools/emul 2019-05-09 14:09:40 -04:00			`$(TARGETS):`
Add tools/emul 2019-05-09 12:58:41 -04:00			`cc $< libz80/libz80.o -o $@`

			`libz80/libz80.o: libz80/z80.c`
			`make -C libz80/codegen opcodes`
			`gcc -Wall -ansi -g -c -o libz80/libz80.o libz80/z80.c`

zasm emul: add tooling for includes fsdev On build, pack `parts/z80` into a CFS and embed it into the emulated zasm executable as an fsdev. This will allow for the upcoming include directive to have something to go to. For now, this is useless except for inflating the emulated zasm's size. 2019-05-16 12:07:57 -04:00			`$(CFSPACK):`
tools/emul/shell: add filesystem support With the help of the newly-introduced cfspack tool, we can mount a filesystem in our emulated shell and play around. Read-only for now. Unpacking incoming. 2019-05-12 11:20:31 -04:00			`make -C ../cfspack`

Add tools/emul 2019-05-09 12:58:41 -04:00			`.PHONY: clean`
			`clean:`
tools/emul: clean up the place a bit 2019-05-17 07:23:59 -04:00			`rm -f $(TARGETS) $(KERNEL_HEADERS) $(USER_HEADERS) zasm/includes.*`