laserbeak43 wrote:i get all kinds of crazy errors now, I've attached images of them.
Darn, so much for that idea, looks like Intellisense can't parse gcc headers terribly well.
laserbeak43 wrote:also, in C:\devkitPro\devkitPPC\lib\gcc\powerpc-eabi\4.4.3\, there's an include and an include-fixed. which one do i use?
It should be just include, unfortunately it looks like allowing Intellisense to parse the gcc headers is a bad idea.
I've just had a play around with the VS2010 Express edition - I removed the VC search paths to get IntelliSense using the gcc headers instead but that's even worse, it doesn't understand a lot of the newlib headers which results in errors for a lot of standard functions. Things look a lot better if you remove the gcc paths and stick with just adding the libogc include path then right click the error window and untick "Show IntelliSense Errors".
Unfortunately it looks like VS2010 doesn't capture the error and warning output from make so the exercise was a bit pointless :/ You might be better using 2k8, things seem to work a lot better there.