devkitPro

I know it sounds like a bit of a cop out but ... when it's done. Testing is under way with both 4.2.3 and 4.3.0 but there are some other factors affecting the r22 release.

What host OS are you using?

Wait for devkitARM to use 4.3.0. We don't encourage or support gcc versions other than those in the current stable releases.

I'm not quite sure what you mean.

There have been some recent reports of files not being properly downloaded from sourceforge though. You could try deleting the libnds .tar.bz2 file the installer downloaded & see if that helps.

The HAVE_INITFINI_ARRAY thing is a newlib problem, it can't be built with make 3.81. I usually build with a local make 3.80 added temporarily to the path while building devkitARM. I may have messed up the packaging of the buildscripts for devkitARM as well, sorry. I'm hoping to release devkitARM r22...

Sorry no, not at this time.

We have more than enough to do with the current toolchains and, unfortunately, supporting a linux target in a windows environment is a rather specialised and difficult task.

Oops, looks like I missed that in the final check of libogc examples before the release. I'll correct this soon and hopefully run a new release of the examples fairly soon when I add some extra sample code.

Yes there are plans to do exactly that. We're currently in the process of adding wii/cube SD support to Chishm's rather excellent libfat which will allow access to both the internal SD card and USBgecko via stdio.

Sorry to take so long getting to this, it's been a busy couple of weeks. The models were exported using custom plugins for proprietary tools like 3DS Max and Maya. Unfortunately it's not permissable to distribute these and we did plan to eventually find something we could distribute but still haven'...

You can use memalign instead of trying to align pointers from malloc manually - that way you can free it directly if you need to instead of storing the original pointer. Have you managed to narrow down the location of the fault any? Even finding out which source file is causing the problem can help ...

What we're doing with the VS wizards being worked on is to read the templates from their installed location ( <path/to/devkitPro/examples/<platform>) to avoid having to update the wizard when we update the templates. You can find them in the SF downloads @ http://sourceforge.net/project/showfiles.ph...