luxferre/equi
1
0
Fork 0
Code Actions Activity

Apple IIe config figured out

Browse Source
This commit is contained in:
Luxferre
2022-08-14 21:26:04 +03:00
parent 71eb5bafa8
commit 984ced3396
3 changed files with 8 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -4
View File
@@ -172,12 +172,12 @@ Equi's codebase detects TCC and attempts to save size by linking against tcclib
tcc -std=c89 -o equi equi.c [-DSTACK_SIZE=... ...]
```
### Building with CC65 for Enhanced Apple IIe: `make apple2enh`
### Building with CC65 for Enhanced Apple IIe: `make a2`
This is where things start to get interesting, as we need to specify the exact target machine for CC65 and perform certain target-dependent post-build manipulation. For now, Equi reference implementation is only being tested for 65C02-based Enhanced Apple IIe (as the earliest model both supported by CC65 suite and supporting lowercase character I/O), so the command to build it would be:
```
cl65 --standard c89 -O -Os -t apple2enh -o equi.a2enh equi.c
cl65 --standard c89 -O -Os -t apple2enh -o equi.a2enh [-DSTACK_SIZE=... ...] equi.c
```
Then, if there are no compiler/linker errors, we can proceed with building the image (assuming we're using Java and AppleCommander with an empty 140K ProDOS 8 image bundled in the repo for image assembly):
@@ -196,8 +196,6 @@ You can also add a 96K-sized `PERS.DAT` file shipped in the repo to use the pers
java -jar platform-build-tools/apple2/ac.jar -dos equi.dsk PERS.DAT bin < platform-build-tools/PERS.DAT
```
The Makefile also provides a usual `apple2` target and the disk image will run on a "normal" Apple IIe, however the environment is not guaranteed to work correctly due to the way CC65 compiler converts string literals for this target.
## FAQ
### Why does the world need another Forth-like system?