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?

Thanks, it's commited to the SVN head and will be shipped in the next SDK release. KEY_NSPIRE_CAPS is now deprecated.
The key constants are based on http://hackspire.unsads.com/wiki/index.php/Keypads , there might be other mistakes.

sorry about that. Can you tell me if r684 is ok for you?

tangrs's blog describes and the additional setup and missing stub functions.

Getting C++ on the TI-Nspire currently requires several additional setup steps and has specific limitations. Moreover C++ is not originally design for embedded programming (but it doesn't mean it can't be used or is not recommanded).
If you want to start developping for the TI-Nspire as a beginner, C will be much easier.

You don't really need to learn C: since C++ is a superset of C, you actually already know it. Just pick up a guide which compares C and C++ to find what you should not use when developing in C. There are plenty of those available.

32-byte alignment seems like it would be pretty standard for ARM programs.

Ok. Anyway it's not that difficult to add to Ndless.

If the BFLT converter is based on that ELF loader, though, it might be missing some relocation cases.

The loader depends on the standard elf2flt, whereas the ELF loader was entirely written by tangrs. I don't know which cases were missed for you, but hopefully elf2flt is more complete.

I'm not sure how much lighter BFLT would make it, either (it does define the .bss section by size and not a bunch of zeroes, right?)

Yes much problably, although I haven't tested: https://github.com/tangrs/ndless-bflt-loader/blob/master/bflt/bflt.c
According to tangrs the binaries are much lighter.

calc84maniac, would the integration of tangrs's BFLT loader to Ndless make the emulator lighter (there's a patch ready for it, and its much more simple that the ELF loader), even if you still need to align the malloc yourself? (I'm not sure if making a 32-byte alignment the default in Ndless would make sense for all programs).

What is the name of the file?