#177502 - Bregalad - Thu Jul 12, 2012 11:15 am
I'm sorry if what I'm asking sounds trivial.
I'm trying to get started to GBAdev. Most tutorials for the GBA uses the old devkitgba instead of the new devkitarm.
Supposedly it's roughly equivalent but I have trouble following the tutorials, I'm trying to get started like they describe here.
Of course I replace "gcc" and "objcopy" by "arm-none-eabi-gcc" and "arm-none-eabi-objcopy" respectively.
I get no errors, but the resulting GBA rom refuses to run in an emulator.
This works fine using the devkitpro's template, BUT I don't understand how their incredibly complex makefile works, and I'd like to have the freedom to compile my files as I want (and not as THEY want).
(At a later stage I'd like to have different optimisation settings for different .c files, and chose which files are compiled in ARM or THUMB mode).
Thanks in advance for any help.
I'm trying to get started to GBAdev. Most tutorials for the GBA uses the old devkitgba instead of the new devkitarm.
Supposedly it's roughly equivalent but I have trouble following the tutorials, I'm trying to get started like they describe here.
Of course I replace "gcc" and "objcopy" by "arm-none-eabi-gcc" and "arm-none-eabi-objcopy" respectively.
I get no errors, but the resulting GBA rom refuses to run in an emulator.
This works fine using the devkitpro's template, BUT I don't understand how their incredibly complex makefile works, and I'd like to have the freedom to compile my files as I want (and not as THEY want).
(At a later stage I'd like to have different optimisation settings for different .c files, and chose which files are compiled in ARM or THUMB mode).
Thanks in advance for any help.