devkitPro

Hello,
i've been recently working on a way to integrate the devkitPPC toolchain into Eclipse. I ended up writing a plugin that may be usefull to others as well.

The plugin adds the devkitPPC Toolchain to the CDT Managed Build System. Once the plugin is installed the devkitPPC toolchain will become available for C/C++ projects whose final build artefact is either an executable or static library. If you choose the devkitPPC toolchain for a project, the build artefact will be created using the DevkitPPC tools (compiler, linker, archiver, ...). The plugin will figure out builtin compiler specs (builtin include paths, macros...) and will also add the libogc include path, -library path, -library to the projects compiler resp. linker settings.

Requirements:

• Platform: Win, Linux, Mac (Mac is untested)
• a recent Eclipse Helios or Indigo installation
• devkitPPC
• DEVKITPRO/DEVKITPPC environment variables pointing to the particular installation folders if devkitPPC is not installed to the following default locations:
  • c:\devkitPro resp. c:\devkitPro\devkitPPC for Windows
  • /opt/devkitpro/ resp. /opt/devkitpro/devkitPPC for Linux & Mac

Installation:
Use the WiiClipse Eclipse Update Site: http://wiiclipse.github.com/update-site/ (via Eclipse->Help->Install New Software)

Quickstart:

• Install plugin via update site
• Create a new C/C++ project -> "Empty project"
• Choose the "devkitPPC GCC" toolchain from the list of availabe toolchains

Interesting, I'm not particularly keen on managed builds though - they make things rather awkward for people who don't use the same IDE to compile. This is one of the reasons for the crazy Makefiles we provide - they work in any IDE that can make use of a custom Makefile (including Eclipse fwiw).

I'm also currently in the process of getting CodeLite prepared to be the IDE we provide as part of the install so this isn't really something we'd really be prepared to encourage or support, especially considering an Eclipse install is larger than all the tools we provide put together.

http://wiiclipse.github.com/update-site/ appears to be a broken link. It would be much appreciated if you could replace the phrase "using the devkitPro toolchain" with "using the devkitPPC toolchain provided by devkitPro" on http://wiiclipse.github.com. devkitPro isn't a toolchain, it's more of a brand.

Sorry I'm not as excited as you are about this, it looks like a great piece of work and you've obviously put a lot of effort in.

Hello,

WinterMute wrote: It would be much appreciated if you could replace the phrase "using the devkitPro toolchain" with "using the devkitPPC toolchain provided by devkitPro" on http://wiiclipse.github.com. devkitPro isn't a toolchain, it's more of a brand.

I fixed that. Thanks for pointing out the misunderstanding.

WinterMute wrote: http://wiiclipse.github.com/update-site/ appears to be a broken link.

The URL is meant to be used from within Eclipse to install the plugin. It hosts a simple xml file. Until now there was no index page. So thats why your browser came up with a dead link. anyway i added a simple index page for browsers to minimize confusion.

WinterMute wrote: Interesting, I'm not particularly keen on managed builds though - they make things rather awkward for people who don't use the same IDE to compile. This is one of the reasons for the crazy Makefiles we provide - they work in any IDE that can make use of a custom Makefile (including Eclipse fwiw).

I totally understand your points. I just want to point that Managed Builds or automatic make file generation is optional in Eclipse. So you can still use existing Makefiles with the plugin. The main purpose of the plugin is to make creation/configuration of new projects as easy as possible.

Also, sorry for double posting the initial post. I didn't realize the forums were moderated.