Inspired by Chronicles, Jibby allows you to configure various ROM setttings at compile-time through command line parameters.
The available parameters are as listed in the Consts section below, but with "gb" prepended to it.
Example:
-d:gbAllocType=FreeList -d:gbRomTitle='HELLO WORLD'
Some of these configurations require the wrapper tools to be rebuilt, so you may want to delete the .tools/ subdirectory beforehand.
Consts
codeStart: int = 336
-
where in ROM should the compiled code startNote: requires tool rebuild.
compilerMaxAlloc: int = 50000
-
controls SDCC's --max-alloc-per-node setting. higher value = better code gen but longer to compile.Note: requires tool rebuild.
dataStart: int = 49312
-
where in WRAM should variables goNote: requires tool rebuild.
heapSize: int = 256
-
the size of the dynamic heap available to the malloc function.Note: requires tool rebuild.
romTitle: string = ""
-
Name to use inside the ROM headerNote: requires tool rebuild.
stackStart: int = 57344
-
where in WRAM should the stack grow fromNote: requires tool rebuild.
useAsmProcs: bool = false
-
whether or not some procs should use the assembly version.
currently affects:
- nimMemory: nimCopyMem and the memcpy function.
- init: initNimRuntimeVars.
useGbdk: bool = false
-
if we are using GBDK's librariesNote: requires tool rebuild.
virtualSpritesStart: int = 49152
-
where in WRAM should the virtual OAM startNote: requires tool rebuild.