devkitPro

I have used GlovePie for WiiMote use on my computer. It works great.

I don't see anything immediately problematic in this code. Possibly a bug in nitro filesystem code. Although there is one case in your code that you should be doing closedir():


if(num < 2)
{
Log::Debug("No songs found\n");
closedir(pdir); // whoops you forgot to close here
return 0;
}


I ...

A value never gets destroyed. A variable is storage for a value.

I fixed a bunch of this crap, thanks to your findings. Currently, maxmod will fail, but WinterMute will be fixing that soon. After that, the buildscripts should work no problem, assuming you have all the prereqs (I added libusb to the README)

http://devkitpro.git.sourceforge.net/git/gitweb.cgi?p ...

As you guys said, yes, any variable created inside { and } is used only inside { and } and then destroyed as it gets to }.

That's exactly right.


Pretend that there is a variable (with a value of 5) created outside that scope that has been set to one.
Then that variable is changed to another ...

See my first post. It explains it.

Do int a = 0 on the outside. Then inside do a=5.

Of course! Just perform the declarations above (outside of) the if blocks.

static void *xfb = NULL;


This line? It does the following things:

1. Declare a variable xfb
2. xfb is of type void* (a pointer to void, i.e. a pointer to generic/unknown type)
3. Assign the value NULL to xfb (NULL is ((void*)0) in GNU)
4. xfb is static (other translation units will never be ...

if (bp1 & WPAD_BUTTON_MINUS ) {
int a = 5; // you declare a new variable 'a'
buttoncheck++;
} // 'a' ceases to exist after this curly brace. it now goes "out of scope"
c:/users/n**/desktop/devkitpro/examples/wii/template/source/template.cpp:128:8: warning: unused variable 'a' [-Wunused ...