Extra steps
To test that everything is working, you can try building one of the examples or project templates included in BlocksDS.
There is a template that lets the programmer write the code for both CPUs of the
NDS (rom_combined) and a template that uses the default ARM7 core that comes
with Blocks DS and lets the programmer focus on the ARM9 core (rom_arm9).
There are also two templates to create static libraries.
For example, go to the combined template folder and build it:
cd templates/rom_combined
make
This should have generated a NDS ROM that you can run on any emulator or flashcart.
To do a verbose build, run make like this (this also works for the Makefile of
the SDK):
VERBOSE=1 make
NOTE: The paths in the Makefile that refer to source code, includes,
graphics, data, etc, must be inside the folder of the project. That means you
can’t use .. in a path to go one level up from the Makefile. If you really
need to use folders outside of the folder of the project, create a symlink to
the destination, or build the other code as a static library and link it with
the project.
This document has a list of tools and libraries that
support BlocksDS and can be installed in /opt/blocksds/external.
You may keep multiple versions of this SDK in your PC. The location of the
active SDK is stored in the environment variables BLOCKSDS and BLOCKSDSEXT,
so all you need to do is to change their values and point to the version of the
SDK you want to use.
By default, the paths are assumed to be /opt/blocksds/core/ and
/opt/blocksds/external/. The first one is used for core BlocksDS libraries
and tools, and it is managed by BlocksDS. The second one is left for users to
freely install third party libraries and tools.