How markmoxon/elite-source-code-commodore-64 works
Main Components
a) Build System Components:
• Source Files (1-source-files/)
• Build Scripts (2-build-files/)
• Assembly Output (3-assembled-output/)
• Reference Binaries (4-reference-binaries/)
• Game Disk Images (5-compiled-game-disks/)
b) Game Components:
• Main Game Code
• Loader System
• Graphics System
• Music System
• Data Files
[Source Files] -> [Build Scripts] -> [Assembled Output] -> [Game Disk Images]
• [Reference Binaries]
• (for verification)
[Loader System]
[Main Game Code] <-> [Graphics System]
[Music System] <-> [Data Files]
[Low Memory] -> [Game Code] -> [High Memory]
[LOCODE.bin] [Game Data] [HICODE.bin]
Important Relationships
a) Build Process:
• BeebAsm compilation flow
• Python script processing
• Checksum verification
• Disk image creation
b) Game Components:
• Memory management between code segments
• Data flow between game systems
• Resource loading paths
Technical Details to Note
• Assembly source files (.asm)
• Binary data files (.bin)
• Build scripts (Python, Make)
• Disk image format (.d64)
The variant handling system
Keep the focus on the assembly and build process, as this is primarily a development tool project rather than a runtime system.
This structure will help developers understand both the build process and the game's architecture while maintaining historical accuracy to the original Commodore 64 Elite implementation.