mateusfavarin / psx-modding-toolchain Goto Github PK

As the title suggests I would like to request to allow you to specify custom compiler flags in the config.json file. This would be useful in my project where I need the -fshort-enums flag.

I'm unsure how reasonable this would be, but I was thinking if there could be a way to automatically determine the address to compile .c files for (based on user-defined memory ranges)?

Basically I have several smaller mods for a game, and compiling them each one by one works fine. However the issue comes when I want to combine multiple of them. Now if these mods don't share any of the same addresses for the .c files then it works fine, but it's a lot of work manually managing that. It means constantly checking the size of the output and seeing where in the exe there's enough of unused space to place that specific mod.

What I would propose would be in the buildlist to be able to set the address to auto and then somewhere else, like the config, you can specify available memory ranges which can be used. In my case this would consists of a lot of memory ranges in the exe where there are unused functions (mostly unused Psyq functions) which mods can freely overwrite. Then there'd be an option to build multiple mods at once where it'd make sure each mod uses a unique address from the range that fits the size of that mod.

I generally dont need the standard library (with this situation being the one exception) but when ever I try to use a regular C function like abs or sprintf the address gets complete messed up and Im not even sure if the function is even being compiled at all . I thought the Tool was suppoused to just put the extrac lib functions in the first file in buildlist.txt