From: shankar@chromatic.com (Shankar Unni)
Subject: Re: cygwin.dll
17 Jan 1997 20:49:52 -0800
Approved: cygnus.gnu-win32@cygnus.com
Distribution: cygnus
Message-ID: <32DFC713.20267199.cygnus.gnu-win32@chromatic.com>
References: <c=US%a=_%p=E-Stamp%l=MERCURY-970116223207Z-1609@mercury.e-stamp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.18 i586)
Original-To: James Osburn <james_osburn@e-stamp.com>
Original-CC: gnu-win32@cygnus.com
Original-Sender: owner-gnu-win32@cygnus.com

James Osburn wrote:

> First the cygwin.dll is to large It should not
> contain the unix to win32 interface. 

Folks: cygwin.dll is *NOT* that large. If you run "size" on it, you'll
see that the active parts (text+data+bss) are actually only 330K (not
3MB). The size of the file is obviously due to debug information and the
like, but 3MB are *NOT* being loaded into memory. So relax.

I'm sure the production cygwin.dll will be much more svelte (shouldn't
be much more than 500K, if compiled without -g). There should be a
separate cygwindebug.dll with full debug information, for those who want
to debug their programs and step into the libraries.

-- 
Shankar Unni                                  shankar@chromatic.com
Chromatic Research                            (408) 752-9488
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
