collapseos/tools/emul/Makefile

TARGETS = shell/shell zasm/zasm runbin/runbin
CFSPACK = ../cfspack/cfspack
KERNEL = ../../kernel
APPS = ../../apps
ZASMBIN = zasm/zasm

.PHONY: all
all: $(TARGETS)

shell/kernel.h: shell/shell_.asm $(ZASMBIN)
	$(ZASMBIN) < $< | ./bin2c.sh KERNEL | tee $@ > /dev/null

zasm/kernel.h: zasm/kernel.bin
	./bin2c.sh KERNEL < $< | tee $@ > /dev/null

zasm/user.h: zasm/zasm.bin
	./bin2c.sh USERSPACE < $< | tee $@ > /dev/null

zasm/includes.cfs: $(CFSPACK)
	rm -rf zasm/includes
	cp -r $(KERNEL) zasm/includes
	cp -r $(APPS)/zasm zasm/includes/zasm
	find zasm/includes -name *.md -o -name *.example -o -name glue.asm -delete
	find zasm/includes -type f -exec sed -i -e 's/;.*//g' {} \;
	cp user.h zasm/includes
	$(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)
$(ZASMBIN): zasm/zasm.c libz80/libz80.o zasm/kernel.h zasm/user.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: updatebootstrap
updatebootstrap: $(ZASMBIN)
	$(ZASMBIN) < zasm/glue.asm > zasm/kernel.bin
	$(ZASMBIN) < $(APPS)/zasm/glue.asm > zasm/zasm.bin

.PHONY: clean
clean:
	rm -f $(TARGETS) zasm/{kernel,user}.h shell/kernel.h 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`
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 /parts/z80 to /kernel Let go of that "meta os" thing. it's not as meta as I made it sound like. It's a kernel. 2019-05-19 11:19:41 -04:00			`KERNEL = ../../kernel`
zasm emul: get rid of the kernel/user distinction Made things complicated for nothing. 2019-05-19 09:14:40 -04:00			`APPS = ../../apps`
zasm now bootstraps itself without scas! 2019-05-19 15:03:34 -04:00			`ZASMBIN = zasm/zasm`
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
Make the shell emulator be built by zasm 2019-05-20 07:29:19 -04:00			`shell/kernel.h: shell/shell_.asm $(ZASMBIN)`
			`$(ZASMBIN) < $< \| ./bin2c.sh KERNEL \| tee $@ > /dev/null`
zasm emul: bring back kernel/user distinction It was a bad idea to remove it. Now that I'm introducing the concept of a per-app glue file, it becomes much easier to build emulated zasm as a userspace app. 2019-05-19 12:57:59 -04:00
zasm now bootstraps itself without scas! 2019-05-19 15:03:34 -04:00			`zasm/kernel.h: zasm/kernel.bin`
			`./bin2c.sh KERNEL < $< \| tee $@ > /dev/null`

			`zasm/user.h: zasm/zasm.bin`
			`./bin2c.sh USERSPACE < $< \| 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`
Move /parts/z80 to /kernel Let go of that "meta os" thing. it's not as meta as I made it sound like. It's a kernel. 2019-05-19 11:19:41 -04:00			`cp -r $(KERNEL) zasm/includes`
			`cp -r $(APPS)/zasm zasm/includes/zasm`
zasm now bootstraps itself without scas! 2019-05-19 15:03:34 -04:00			`find zasm/includes -name .md -o -name .example -o -name glue.asm -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' {} \;`
zasm emul: bring back kernel/user distinction It was a bad idea to remove it. Now that I'm introducing the concept of a per-app glue file, it becomes much easier to build emulated zasm as a userspace app. 2019-05-19 12:57:59 -04:00			`cp user.h zasm/includes`
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 now bootstraps itself without scas! 2019-05-19 15:03:34 -04:00			`$(ZASMBIN): zasm/zasm.c libz80/libz80.o zasm/kernel.h zasm/user.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`

zasm now bootstraps itself without scas! 2019-05-19 15:03:34 -04:00			`.PHONY: updatebootstrap`
			`updatebootstrap: $(ZASMBIN)`
			`$(ZASMBIN) < zasm/glue.asm > zasm/kernel.bin`
			`$(ZASMBIN) < $(APPS)/zasm/glue.asm > zasm/zasm.bin`

Add tools/emul 2019-05-09 12:58:41 -04:00			`.PHONY: clean`
			`clean:`
zasm now bootstraps itself without scas! 2019-05-19 15:03:34 -04:00			`rm -f $(TARGETS) zasm/{kernel,user}.h shell/kernel.h zasm/includes.*`