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

[Diogenes <phathax0r@gmail.com>]

Managed to get some small apps running with my custom runtime. Things are going well, for a hack job. Because that's what I have right now, a hack job. Calling my little project here the "HackTime" runtime, because apparently I'm not doing it the "proper" way.

So I figure I'd best eat a little humble pie before my hacks grow out of control. :->

For the moment I'm just doing a custom shaved down runtime for my platform (Debian stable). Enough to get familiar with the innards of the GNAT runtime and the GNAT compiler toolchain.

I can get it to start using a linker script, but this isn't exactly elegant. So what IS the proper way to link in startup code for just a simple native runtime environment. I'm not porting it, yet. Should I just write the "main" procedure in C and be done with it?

Also, if I want to make it "fast"; instead of linking with crt1.o can I just override the calls to the C Library with direct calls to the Linux kernel? Such as overriding "adainit" with a call to "execve()".

Furthermore...for system.ads...just to be certain, I should be able modify most settings defined in targparm.ads without totally breaking the system. Yes?

Also...the docs seem to indicate that we can't add Ada.Finalization packages to a Configurable Runtime. Am I reading that right? So no Storage_Pools? 

Better make sure I got this right before I move on to a serious runtime project.

Any advice would be appreciated. Thanks.