From:	dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Subject:	Re: Why is cygwin.dll?
16 Jan 1997 11:33:42 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<009AE761.42405F80.7322.cygnus.gnu-win32@ifk20.mach.uni-karlsruhe.de>
Original-To:	jqb AT netcom DOT com
Original-CC:	gnu-win32 AT cygnus DOT com, dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Hi, you wrote:

: Ben Constable wrote:
: >
: > > Now, figure on programs like grep.exe (91,648 bytes) having to include
: > > that library in their .EXE...grep is now 3 megs, instead of 91k.
: >
: > No. That is totally wrong. Go compile grep or a similar program with watcom
: > or visual C++. You will find that they do not have to be that big. It is
: > because when you link the program, you only link the bits you need.

: Any university offers courses that will cover the tradeoffs between
: dynamic and static libraries; it seems some readers of this group
: could benefit from such an education.  Given a static cygwin library
: (but we *aren't* given one, not yet), the sum of the sizes of all the
: executables linked with such a library would be considerably greater
: than the current distribution.  Not nearly 3M * 120 greater, true.

What was not mentioned yet is that a DLL is only loaded once into RAM and
shared by multiple processes. So you occupy never more than 3MB RAM
regardless of how many processes are running at the same time.
And even then a modern OS need only to page in that parts actually used.


Bye, Heribert (dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de)
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -