Hi,

I need CLib to be available prior to calling ShellAppMain that way all the
CPP static constructors and any pre main setup stuff (mounting file system
which may want to use stdlib functions, etc..) can be done.  So my thought
is to take part of ShellAppMain and make it __ctor_CLib for init and
__dtor_CLib for term (but leaving the file close processing in ShellAppMain
because any file access would be coming after the __ctor at this point).
Then other things can also be __ctor and depend on CLib (just right now
anything wanting file access would fail since nothing mounted)..  However
looking at some of the other constructors in stdlib, such as devshell, they
depend on CLib whereas I would think CLib should depend on it (for
construction ordering anyway).  I think for now I'll just not make cpp
initialization and the others a constructor, but call them in the program
entry point prior to ShellAppMain being called because I don't know where
you guys are going with the version that removes shell dependance and don't
want to move too far away for updates (I've already detached from the shell
myself .. pretty easy, from what I recall replace contents of daShell,
comment out the get/put env and link to your own.).   Any updates?  May
want to look at using a constructor for clib (main) and check constructor
ordering...
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to