Basically, the bin/ directory disappeared, so I tried to find and use another copy of nspire-gcc within another directory. I only found tools/build/nspire-gcc, so I set my PATH to that, and it failed (for obvious reasons). Building ndless itself failed too!

The recommended way is to download the full trunk and use Ndless-SDK/ndless/bin. I'll see if I can separate the tree, but it won't be easy, since the Windows SDK needs the files (and others) in its tree.

I do have a few minor suggestions though

Thanks

A pretty, yet thorough wizard for getting an emulator set up and ready to go.

The SDK embeds nspire_emu and PolyDumper, and the setup only requires dropping the boot images and OS files in a directory. But if it can be made even easier, any suggestion is welcome.

Tutorials using the 3rd party libraries.

Sure, I may start a series of tutorials.

Add nRGBLib to the 3rd party libraries.

Why not, if nSDL is too hard to use or too limited.

Clarify that the printf() statement does NOT print to screen, and that something like NspireIO should be used. In fact, maybe it would be best to replace that printf() tutorial with a NspireIO one (using the NspireIO printf() statement)!

All the samples provided are now nspireio2-based or SDL-based... but I forgot to update the Linux hackspire page.

Better API documentation + tutorials. Each function could have their own page, with a description, usage, breakdown of usage, and maybe a very well documented example (with a picture, if applicable!).

Documenting this way requires really much time, which I don't have. Hackspire is open for edition to everyone registered though. But if you are talking about http://hackspire.unsads.com/wiki/index.php/Libndls , if find it quite straightforward.

Pictures on the wiki! I'd feel better than looking at code

Which pages exactly would need improvements with pictures?

Very nice, looks quite useful!

Three notes:
* these non-standard 8-bit, 16-bit and 32-bit type definitions are ugly; standard types defined in the stdint.h header by C99, 13 years ago, are better ;
* I think that you have CharWidth and CharHeight swapped;
* I'd define the array of pixels as a single-dimensional array, so as to ensure that the compiler uses flat storage, instead of an array of CharSetSize pointers triggering as many relocations, and CharSetSize arrays of CharHeight bytes.

Is it possible to use kArmTI as the emulator?  Iirc it's based off of nspire_emu..when I try to launch it windows says it's "stopped working"
Not sure if there would be any special instructions or anything..I copied a working setup and renamed "kArmTI_v**.exe" to "nspire_emu.exe" and it still starts up fine when launched directly.
The stuff's in C:/Ndless so no spaces in the folder name, not sure what else could be going wrong

I didn't see anything mentioning it in the readme but good to know I guess.
Aight time to learn the keys

I didn't see anything mentioning it in the readme

No no no, I ment read 10 times the readme in order to manage to run nspire_emu inside the SDK. Remerber that the nspire_emu inside the SDK handle dil transfert directly from the SDK.

10 times is the number of tries I had to read the readme before nspire_emu actually worked

Is it possible to use kArmTI as the emulator?  Iirc it's based off of nspire_emu..when I try to launch it windows says it's "stopped working"
Not sure if there would be any special instructions or anything..I copied a working setup and renamed "kArmTI_v**.exe" to "nspire_emu.exe" and it still starts up fine when launched directly.

Does it work at least with the official version of nspire_emu provided?

10 times is the number of tries I had to read the readme before nspire_emu actually worked

I will gladly integrate any suggestion to improve the documentation, but you have to tell what was not clear to you.