I understand that we have an underlying clib2 or newlib, which support lots of the lower level "stuff". and I am being vague because I have no more details than that.(file handles? linkage to parents? )
I understand that certain programs, such as tools for Bars&Pipes, or AHI drivers, or auto-starting USB FD drivers often link with "-nostartfiles", which leaves out the clib2 or newlib code and initialization. I think this applies to many libs and devs as well.
I am absolutely sure of NOTHING I have said so far. This is a learning process for me.
Now assuming I am writing, for example, an autostarting usbfd driver, which will be launched automatically when a matching bit of hardware is plugged in.
I can open DOS, Exec, and whatever else I need using the usual methods.
But what about newlib?
Is there a good way to do this? Do I simply open newlib.library and INewlib? is there any other special initialization that I need to do, or are some things forbidden if I opened it myself?
I'm just trying to understand the difference between newlib and the more common libraries we use. Any information would be quite helpful.