configuring codeblocks for devkitARM in Linux

[ac3raven]

http://niozero.blogspot.com/2008/08/tut ... itpro.html

I've been following the above guide to configure codeblocks for devkitARM, but it is a Windows guide and I don't have, nor do I need MinGW/msys.

So I was wondering where to put the installation directory of the compiler. The default is /usr, but I have a feeling that won't work.

I'm in Arch Linux and basically, I need a little bit of guidance setting up codeblocks for devkitARM

[WinterMute]

The default directory for devkitPro toolchains is under /opt/devkitpro as per http://wiki.devkitpro.org/index.php/Get ... /devkitARM. Under no circumstances should you install the toolchains to /usr this is likely to break your native compilers.

Codeblocks is a rather awkward editor to set up - it seems to insist on managing the build process itself and I wasn't able to find a way to use a custom Makefile with it so I find it difficult to recommend. We're currently looking at using Codelite as the standard recommended editor but it still needs a few modifications to work for our needs.

For now you can set up an nds project manually - simply copy the arm9 template from the nds examples then open codelite, click Workspace -> Create New Project. In that dialog select Others for categories, Custom Makefile for template, browse to the folder you just created when copying the template, give the project a name and hit OK. Then click Workspace -> Open Active Project Settings and set the Working Directory to $(ProjectPath) for both debug & release configs. You'll need to add files to the project manually for now but we'll sort this out in due course.

Once we're done with the mods we need we'll have templates in Codelite that'll make this much easier.

[ac3raven]

okay, so where are these nds examples you speak of?

[WinterMute]

Linked from the wiki page I pointed to above ...

[ac3raven]

So would this be a proper project path?
/opt/devkitpro/examples/nds/templates/arm9


I don't understand why I need to "copy" the arm9 directory, and if I am indeed suppose to copy it, where would I paste it?

[WinterMute]

You copy the directory so you have a fresh copy to work with rather than overwriting the example source code. With the windows updater you run the risk of losing all your work since it clears the example directories to avoid stale files. On linux & OSX the /opt/devkitpro folder should really be read only for normal users, in this case you won't be able to compile in place. Generally it's good practice to copy examples elsewhere before modifying them in order to keep a pristine working copy.

Normally you would copy to a folder where you keep your other projects, ~/projects/nds maybe? Also rename the folder to something memorable - the default Makefile creates an nds with the name of the folder for simplicity.