collapseos/tools/emul/Makefile

TARGETS = shell/shell zasm/zasm runbin/runbin
KERNEL_HEADERS = shell/kernel.h zasm/kernel.h
USER_HEADERS = zasm/user.h
CFSPACK = ../cfspack/cfspack
PARTS = ../../parts/z80
APPS = ../../apps

.PHONY: all
all: $(TARGETS)

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

zasm/includes.cfs: $(CFSPACK)
	rm -rf zasm/includes
	cp -r ../../parts/z80 zasm/includes
	cp -r ../../apps/zasm zasm/includes/zasm
	find zasm/includes -name *.md -delete
	find zasm/includes -type f -exec sed -i -e 's/;.*//g' {} \;
	$(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/includes.h
runbin/runbin: runbin/runbin.c libz80/libz80.o
$(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.*
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm 2019-05-17 09:33:20 -04:00			`TARGETS = shell/shell zasm/zasm runbin/runbin`
tools/emul: clean up the place a bit 2019-05-17 07:23:59 -04:00			`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`
zasm emul: get rid of the kernel/user distinction Made things complicated for nothing. 2019-05-19 09:14:40 -04:00			`PARTS = ../../parts/z80`
			`APPS = ../../apps`
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):`
zasm emul: get rid of the kernel/user distinction Made things complicated for nothing. 2019-05-19 09:14:40 -04:00			`scas -o - -I $(PARTS) -I $(APPS) $< \| ./bin2c.sh KERNEL \| tee $@ > /dev/null`
Add tools/emul 2019-05-09 12:58:41 -04:00
zasm: can now assemble zasm/util.asm! 2019-05-17 20:47:43 -04:00			`zasm/includes.cfs: $(CFSPACK)`
			`rm -rf zasm/includes`
			`cp -r ../../parts/z80 zasm/includes`
			`cp -r ../../apps/zasm zasm/includes/zasm`
Make apps folder into a namespace To straighten out includes and to pave the way into zasm being part of the same "include CFS" as parts, we make zasm includes namespaced. 2019-05-17 20:22:32 -04:00			`find zasm/includes -name *.md -delete`
Strip comments out of code before packing CFS This shrinks the CFS size to 21k from nearly 64K. This will allow me to kick the can down the road a bit with regards to supporting storage seek/tell greater than 64K. I'll get to it, but first, I want to assemble zasm with zasm! 2019-05-17 19:54:35 -04:00			`find zasm/includes -type f -exec sed -i -e 's/;.*//g' {} \;`
tools/emul: clean up the place a bit 2019-05-17 07:23:59 -04:00			`$(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 emul: get rid of the kernel/user distinction Made things complicated for nothing. 2019-05-19 09:14:40 -04:00			`zasm/zasm: zasm/zasm.c libz80/libz80.o zasm/kernel.h zasm/includes.h`
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm 2019-05-17 09:33:20 -04:00			`runbin/runbin: runbin/runbin.c libz80/libz80.o`
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.*`