I finally made a nice SDK for making your own GlassOS programs. I will be putting out a signed 8xu for GlassOS as well as pre-compiled tools for connectivity. The doxygen page will be updated with new functions and such, too.

Feedback on making stuff is welcome!

Warning! The documentation for functions is up-to-date AFAIK, but the tutorials are out of date and probably don't work without tweeking. They will be fixed eventually.
Documenation of calls here: http://glassos.sf.net/man/
Don't always have internet? Get the PDF version here: http://glassos.sf.net/man/refman.pdf

Download it here!

Oooh, neat! If I get some time this summer, I'll see what I can do as far as trying to compile some programs for GlassOS. Nice job.

Thanks! Let me know about any questions. I will try to get an updated example in the doxygen pages.

I shall certainly do so. I think it's going to be weird and unsettling to be able to compile C for the TIs without obsessing about bytes and clock cycles, though.

hehe! Make yourself think that you are using TIGCC for making 68k programs It won't seem that bad. Nothing stops you from using asm, however. You make programs about 0x3ff0 bytes large and use about 15KB of ram (plus you can extend and use libraries for 0x3ff0*n).

Ah, but there's currently no way to make good multi-page programs at the moment? What do you mean about libraries, that the libraries can be placed on other pages? That would mean that a program's core code must still be within 16368 bytes, right?

This looks very interesting. I look forward to seeing more progress, and downloading an .8xu.

I chose not to have multi page apps. You can put code that doesn't fit, or is shared, like gcas, into a library. That library has a jump table to all of the functions in it. You can then use a bcall to directly jump to the library.

gCAS2 has the math core in a library (libgcas2.so) and makes calls to it. Works perfectly and is easy to use.

<edit>

A nifty tool will be added, mapstat. When you compile things with SDCC, the assembler dumps a bunch of extra files. One of them, .map, is very useful as it shows all labels (globals) and their locations. Now, when you look at it, there is a lot of extra data there that you don't need, like the start and end varients of labels. You are mostly concerned about how large functions are. Well, mapstat will generate a document showing the size of all functions (without _end and _start duplicates), the percent of space used in the binary by the global, and show it sorted by address and by size. Sample when calling mapstat launcher.map:
Code:
(The above is spaced properly, the tabs didn't convert well in the code tag)

<edit>

doxygen page was regenerated and a PDF was also uploaded. See OP for links.