Kenny1

And, what's that routine you messaged me earlier? You said it was pretty basic?

Hm.
I followed xGal's tut.
I just copied the ASM routine, saved it as a .ASM and then dragged it to, the .bat file, and it produced the .bin file and then, ta-da! Open the .bin file with your Hex editor.

But I still don't know how to insert it.

The .bat.

But when I open it, it just closes suddenly.

No, I don't have... But you can PM me!
And, I will open the "as" file in the compiler link you gave me, right?

So, what now?

Wow, thanks!
And, what tools do I need?

ldrb works the same as strb :D
I think :D

Great work, you can post it on the resources thread I made if you want. Sorry I wasn't much help :P

Yeah, see if you can change it from a table. Just changing it to a signpost is rather dull :P

Well, if you can find the textbox loading routine again, maybe we can do it. To be honest, I'm not really seeing the practical use of this. You can change between textbox styles in a script too.

These offsets don't make sense to me, they're all at the end of the ROM. I don't see how any of them are related to textbox swapping :x

sure

Perhaps, although for tools Windows is the best option. I personally triple boot Linux, OS X Mavericks, and Win7 so I can test across platforms. OS X was a pain to set up though, so unless you *really* need it I would hardly recommend getting it.

I will say that in terms of compiling, Linux is a TON easier to set up than Windows.

I guess. I've gotten it working on Windows before but I'm not sure what's up with your system tbh.

This is probably the line you want:

export PATH := $(DEVKITARM)/bin:$(PATH)

Try throwing that into the RoA makefile and see if that does it.

Hm, perhaps check those makefiles and see how they are calling gcc? I can't really think of much else tbh.

Try copying the gcc.exe to the building directory, or, alternatively, add that bin folder to your PATH variable, which will set up your system to be able to call that executable from anywhere in cmd.exe The latter is a much more long term solution, especially if you plan on building multiple projects.

Ah, if that's the case then try running gcc from the command line. It *should* work. If it doesn't, copy gcc, as, objcopy, and ld to the project directory (where the Makefile is) and rename them to arm-eabi-gcc, arm-none-eabi-as, arm-none-eabi-objcopy and arm-none-eabi-ld. If it did work, try editing the makefile to use those executables instead (ie replace arm-none-eabi-gcc with just gcc)

Ah, I didn't get that one. What's the name of the executable?