Date: Mon, 14 Nov 94 09:39:11 -0500
From: dj AT stealth DOT ctron DOT com (DJ Delorie)
To: UCKO AT VAX1 DOT ROCKHURST DOT EDU
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: Shared libraries

> My understanding of the situation is that the only thing keeping DJGPP 
> from normally using shared libraries is global variables accessed by 
> both the libraries and your program.  Couldn't this be remedied by 
> adding some sort of hook to the startup code to automatically export any 
> desired global variables?  Or is the only legal startup code to be found 
> in (g)crt0.o?  Just wondering...

The biggest problem is that once the program is built and stripped,
you don't know *where* the variables are - strip removes that
information.

The other big problem is that shared libraries are normally loaded by
the OS, and ms-dos is still the OS in this case.  To use shared
libraries, each program would have to have the loader linked into it,
which is almost as much space as the library itself.