izaya/collapseos
1
0
Fork 0
mirror of https://github.com/hsoft/collapseos.git synced 2024-12-26 16:18:05 +11:00
Code Issues Releases Wiki Activity
fca0e79da3
collapseos/emul/Makefile

69 lines
2.1 KiB
Makefile
Raw Normal View History

Add /tools/slatest To update LATEST offset more easily. Will be useful for recipes.
2020-04-03 14:15:43 +11:00
TARGETS = runbin/runbin forth/forth
forth: split forth source into multiple files
2020-03-18 12:44:32 +11:00
# Those Forth source files are in a particular order
Add chained comparison support
2020-04-06 06:11:17 +10:00
FORTHSRCS = core.fs cmp.fs print.fs str.fs parse.fs readln.fs fmt.fs z80a.fs
Add in-memory bootstrapping system This should help with the bootstrapping of non-emulated environment. For example, I have a problem with the RC2014: I can't send it bootstrap info until the ACIA is up. I need to find a way...
2020-04-03 23:31:30 +11:00
FORTHSRC_PATHS = ${FORTHSRCS:%=../forth/%} forth/run.fs
Make makefiles and shell scripts portable It's no longer required to use `gmake` under OpenBSD and shell scripts no longer require bash.
2019-12-10 01:36:38 +11:00
OBJS = emul.o libz80/libz80.o
Add /tools/slatest To update LATEST offset more easily. Will be useful for recipes.
2020-04-03 14:15:43 +11:00
SLATEST = ../tools/slatest
Add stripfc tool
2020-04-05 01:27:21 +11:00
STRIPFC = ../tools/stripfc
Move apps/zasm/emul to tools/emul
2019-05-10 04:09:40 +10:00
Add tools/emul
2019-05-10 02:58:41 +10:00
.PHONY: all
Add /tools/slatest To update LATEST offset more easily. Will be useful for recipes.
2020-04-03 14:15:43 +11:00
all: $(TARGETS)
Add tools/emul
2019-05-10 02:58:41 +10:00
Add stripfc tool
2020-04-05 01:27:21 +11:00
$(STRIPFC):
Add /tools/slatest To update LATEST offset more easily. Will be useful for recipes.
2020-04-03 14:15:43 +11:00
$(SLATEST):
$(MAKE) -C ../tools
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
Add /tools/slatest To update LATEST offset more easily. Will be useful for recipes.
2020-04-03 14:15:43 +11:00
# z80c.bin and boot.bin are not in the prerequisites because they're bootstrap
# binaries that should be updated manually through make updatebootstrap.
forth/forth0.bin: $(SLATEST)
Forth self-bootstraps!!! This commit cuts Forth's dependency on zasm. It now self-assembles its own boot-binary! Things are a bit messy now, I'll clean up later.
2020-04-02 13:19:37 +11:00
cat forth/boot.bin forth/z80c.bin > $@
Add /tools/slatest To update LATEST offset more easily. Will be useful for recipes.
2020-04-03 14:15:43 +11:00
$(SLATEST) $@
Add in-memory bootstrapping system This should help with the bootstrapping of non-emulated environment. For example, I have a problem with the RC2014: I can't send it bootstrap info until the ACIA is up. I need to find a way...
2020-04-03 23:31:30 +11:00
cat forth/emul.fs >> $@
emul: add forth target
2020-03-10 13:26:02 +11:00
forth: add bin dict compilation stage! Big one. This allows us to write higher order words directly in Forth, which is much more convenient than writing post-immediate (see "NOT" structure in diff if you want to see what I mean) structures in ASM. These structures can then be written to ROM (rather than loaded in RAM for definitions loaded at run-time). That's quite a bit of tooling that was added, 2 compilations stages, but I think it's well worth it.
2020-03-12 15:14:44 +11:00
forth/forth0-bin.h: forth/forth0.bin
./bin2c.sh KERNEL < forth/forth0.bin | tee $@ > /dev/null
emul: add forth target
2020-03-10 13:26:02 +11:00
forth: make bin staging process a bit less hackish The goal being to add a new native code dict staging phase.
2020-03-23 12:46:43 +11:00
forth/stage1: forth/stage.c $(OBJS) forth/forth0-bin.h
$(CC) forth/stage.c $(OBJS) -o $@
forth: add bin dict compilation stage! Big one. This allows us to write higher order words directly in Forth, which is much more convenient than writing post-immediate (see "NOT" structure in diff if you want to see what I mean) structures in ASM. These structures can then be written to ROM (rather than loaded in RAM for definitions loaded at run-time). That's quite a bit of tooling that was added, 2 compilations stages, but I think it's well worth it.
2020-03-12 15:14:44 +11:00
forth: make bin staging process a bit less hackish The goal being to add a new native code dict staging phase.
2020-03-23 12:46:43 +11:00
forth/stage1dbg: forth/stage.c $(OBJS) forth/forth0-bin.h
Add in-memory bootstrapping system This should help with the bootstrapping of non-emulated environment. For example, I have a problem with the RC2014: I can't send it bootstrap info until the ACIA is up. I need to find a way...
2020-04-03 23:31:30 +11:00
$(CC) -DDEBUG forth/stage.c $(OBJS) -o $@
forth: improve execution model My approach with RS was slightly wrong: RS' TOP was always containing current IP. It worked, but it was problematic when came the time to introduce RS-modifying words: it's impossible to modify RS in a word without immediately messing your flow. Therefore, what used to be RS' TOS has to be a variable that isn't changed midway by RS-modifying words. I guess that's why RS is called *return* stack...
2020-03-14 07:01:09 +11:00
Add stripfc tool
2020-04-05 01:27:21 +11:00
# We don't really need to use stripfc, but we do it anyway to test that we
# don't mistakenly break our code with that tool. It's easier to debug here.
forth: improve bootstrap process
2020-03-25 12:13:02 +11:00
forth/core.bin: $(FORTHSRC_PATHS) forth/stage1
Add stripfc tool
2020-04-05 01:27:21 +11:00
cat $(FORTHSRC_PATHS) ./forth/stop.fs | $(STRIPFC) | ./forth/stage1 | tee $@ > /dev/null
forth: improve bootstrap process
2020-03-25 12:13:02 +11:00
Add in-memory bootstrapping system This should help with the bootstrapping of non-emulated environment. For example, I have a problem with the RC2014: I can't send it bootstrap info until the ACIA is up. I need to find a way...
2020-04-03 23:31:30 +11:00
forth/forth1.bin: forth/core.bin $(SLATEST)
cat forth/boot.bin forth/z80c.bin forth/core.bin > $@
Add /tools/slatest To update LATEST offset more easily. Will be useful for recipes.
2020-04-03 14:15:43 +11:00
$(SLATEST) $@
forth: add bin dict compilation stage! Big one. This allows us to write higher order words directly in Forth, which is much more convenient than writing post-immediate (see "NOT" structure in diff if you want to see what I mean) structures in ASM. These structures can then be written to ROM (rather than loaded in RAM for definitions loaded at run-time). That's quite a bit of tooling that was added, 2 compilations stages, but I think it's well worth it.
2020-03-12 15:14:44 +11:00
forth/forth1-bin.h: forth/forth1.bin
./bin2c.sh KERNEL < forth/forth1.bin | tee $@ > /dev/null
forth: Forth-ify ROT, a native word! This requires us to significantly adjust our build process, which now has 3 stages.
2020-03-25 04:46:05 +11:00
forth/stage2: forth/stage.c $(OBJS) forth/forth1-bin.h
$(CC) -DSTAGE2 forth/stage.c $(OBJS) -o $@
forth: improve bootstrap process
2020-03-25 12:13:02 +11:00
forth/forth: forth/forth.c $(OBJS) forth/forth1-bin.h
emul: add forth target
2020-03-10 13:26:02 +11:00
$(CC) forth/forth.c $(OBJS) -o $@
Make makefiles and shell scripts portable It's no longer required to use `gmake` under OpenBSD and shell scripts no longer require bash.
2019-12-10 01:36:38 +11:00
runbin/runbin: runbin/runbin.c $(OBJS)
$(CC) runbin/runbin.c $(OBJS) -o $@
Add tools/emul
2019-05-10 02:58:41 +10:00
libz80/libz80.o: libz80/z80.c
Make tools/emul *BSD-friendly
2019-07-12 11:21:54 +10:00
$(MAKE) -C libz80/codegen opcodes
zasm: add support for .fill directive
2019-05-20 22:20:00 +10:00
$(CC) -Wall -ansi -g -c -o libz80/libz80.o libz80/z80.c
Add tools/emul
2019-05-10 02:58:41 +10:00
tools/emul: deduplicate a little bit of C code
2019-12-03 08:35:49 +11:00
emul.o: emul.c
$(CC) -c -o emul.o emul.c
tools/emul/shell: copy user.h in its cfsin This way, we can compile apps from within the shell that run on the shell.
2019-06-03 23:25:47 +10:00
zasm now bootstraps itself without scas!
2019-05-20 05:03:34 +10:00
.PHONY: updatebootstrap
Add /tools/slatest To update LATEST offset more easily. Will be useful for recipes.
2020-04-03 14:15:43 +11:00
updatebootstrap: forth/stage2
cat ./forth/conf.fs ../forth/boot.fs | ./forth/stage2 | tee forth/boot.bin > /dev/null
Add in-memory bootstrapping system This should help with the bootstrapping of non-emulated environment. For example, I have a problem with the RC2014: I can't send it bootstrap info until the ACIA is up. I need to find a way...
2020-04-03 23:31:30 +11:00
cat ./forth/conf.fs ../forth/z80c.fs ../forth/icore.fs | ./forth/stage2 | tee forth/z80c.bin > /dev/null
forth: Forth-ify ROT, a native word! This requires us to significantly adjust our build process, which now has 3 stages.
2020-03-25 04:46:05 +11:00
Add tools/emul
2019-05-10 02:58:41 +10:00
.PHONY: clean
clean:
Add /tools/slatest To update LATEST offset more easily. Will be useful for recipes.
2020-04-03 14:15:43 +11:00
rm -f $(TARGETS) emul.o forth/*-bin.h forth/forth?.bin
Reference in New Issue Copy Permalink