Re: Runtime startup code for the GNAT Runtime...and a bit of humble pie.

[Diogenes <phathax0r@gmail.com>]

Alright...to keep this from becoming another Ada vs <language> thread I'll explain what I'm working on now.

Since I got my first "version" to actually compile and do something, I'm now working on getting it to link with musl libc. Seems like I should still be able to compile and link it with gnatmake(since I'm not porting it to another platform YET!). No?
http://www.musl-libc.org/

However...

I would eventually like to get a port going to the Android platform. Seems like that's a place that could really use some high quality code. And the only place where GNAT seems to have a fit is in the binding/linking stage. Should we consider writing separate binder/linker utilities that are somewhat more flexible with the kind of system we're building for? Which leads me to my next train of thought...

Linking with C isn't necessarily bad(although I don't particularly like glibc) as long as your not too dependent on that library, and the library is a good one. 

For this iteration of my runtime project I'm focusing on size.
http://www.fefe.de/dietlibc/diet.pdf
Seems like given that the runtime is being compiled on it's native platform, linking it to a different C Runtime should be trivial.

My next step is a bare bones runtime.

Am I assuming too much here?