Thanks! Well this is being developed in Codex Desktop/ChatGPT with 5.6 SOL as model, I instructed it to make Amiga games in C / lowlevel and started from there and from scratch. Now many hours later we have a complete toolchain. Because I'm a software engineer I do regularly check what is being produced in code in VSCode which sometimes determines my next prompt/question
I just let Codex summarize the the complete toolchain/dev-env:
- C — the main programming language for the game and direct Amiga hardware control
- VBCC — cross-compiles the C code for the Motorola 68020
- VASM — assembles the generated and low-level 68k code
- VLink — links everything into the final Amiga executable
- AmigaOS NDK — provides the AmigaOS headers, system structures and hardware definitions
- GNU Make — automates asset generation, compilation, testing and release builds
- Python and Pillow — convert artwork into Amiga palettes, bitplanes, sprites, masks and packed runtime assets
- Git — version control and development history
- FS-UAE — emulator testing at both 68020 and 68030 configurations
- Real hardware — final testing on an A1200/68030
- ADF, HD and WHDLoad packaging tools — create bootable floppy images and installable release packages
The game is mostly written in C rather than handwritten assembly, but it directly controls the Copper, Blitter, hardware sprites, DMA and Paula audio.