Please leave suggestions on the talk page instead of editing directly, for now.
The [http://www.eclipse.org/ Eclipse Platform] is a modern open source IDE with a built-in debugger GUI and support for several programming languages via plug-ins. Plug-ins can also be used to extend functionality. For many, programmer's notepad and insight will suffice, but others may find the combination a little out of date. This wiki will guide you through each stage in the setup process, but assumes that you are using Windows, have already installed [[
DevkitPro]] and are relatively familiar with the concepts of developing Wii Homebrew. I hope it is of use to others ~ [[User:PhoenixTank|PhoenixTank]] | [[User talk:PhoenixTank|talk]] | [[Special:Contributions/PhoenixTank|contribs]] |
== Requirements ==
*You now see the main IDE with Project Explorer, File Editor, Console and others panes.
*There will be an error and a probably warning in the problems pane. Don't worry about them for now, and open C:\devkitPro\examples\wii\template\ in Windows Explorer. Select the Source folder and makefile, and copy them to clipboard. Return to Eclipse, right click the HelloWorld project in Project Explorer, and paste. The files should now be a part of your project.
*Head to Projects > Properties, or do the same from the right click menu of
helloworld. Click ''C/C++ Build'' then choose the ''behaviour'' tab. Here, change the value of ''Build (Incremental Build)'' to ''build'', then hit OK.
*With default settings, Eclipse will immediately build your project. The error should no longer be there to pester you.
*If you have a warning like: Error launching external scanner info generator (gcc -E -P -v -dD C:/WiiDev/projects/.metadata/.plugins/org.eclipse.cdt.make.core/specs.cpp) then the easiest way to fix this is to add C:\devkitPro\devkitPPC\powerpc-gekko\bin; to the start of your [[#Path|path]] environment variable.
*Right click the project name and choose "Add Make Target".
*Enter Wiiload (or another name) into the first box, and "run" in the second box and hit create.
Provided you have wiiload set up correctly, double clicking this will allow you to easily send your most recently compiled .dol/.elf to your Wii.
== More Settings ==
*C/C++ ¬ Code Style. I use BSD/Allman, but the other most common styles are there too.
*C/C++ ¬ Editor ¬ Content Assist. Drop the delay to 200 ms.
*C/C++ ¬ New CDT project wizard ¬ Makefile Project : Behaviour tab. Uncheck ''Build on resource save'', change value of ''Build (Incremental Build)'' to ''build''
== Debugging ==
In order to debug a Wii application, you have to connect your debugger to it somehow. Your options consist of the use of a USB Gecko or a libogc wifi patch. Either way, the base setup is the same.
*Head to Run > Debug Configurations. Select ''Zylin Embedded debug (Native)'' and create a new configuration.
*Name it GDB
(or other relevant name), and enter the path C:\devkitPro\devkitPPC\bin\powerpc-gekko-gdb.exe .
==== USB Gecko ====
==== Wifi Debugging Patch ====
AKA "The poor man's USB Gecko". This takes a little work to implement, but at a total cost of £0, who can complain?
You'll need to be familiar with checking out from a SVN, patching source files, and compiling libogc from source.