From: jqb AT netcom DOT com (Jim Balter) Subject: Re: Why is cygwin.dll? 17 Jan 1997 20:21:40 -0800 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <32DFE2EB.7A01.cygnus.gnu-win32@netcom.com> References: <970117045612 DOT 1719 AT cse DOT unsw DOT edu DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01Gold (WinNT; I) Original-To: Ben Constable Original-CC: Jeremy Blackman , "M.Carter" , gnu-win32 AT cygnus DOT com Original-Sender: owner-gnu-win32 AT cygnus DOT com Ben Constable wrote: > > > Yes, but my understanding was that many of the functions in cygwin.dll > > are required. At least for complex applications. I know this because I > > tried linking in only what I needed, and my 1 meg executable STILL grew > > to 3.5 (granted, not the 4 I projected, but still pretty honkin' huge). > > NT has a hell of a lot of stuff in it's API's. Stuff like printing > characters, opening sockets and the such are all supported. I do not know > that much about unix, but just what does unix have that requires 3.5MB of > code to emulate for a few functions? Why not go off and read the documentation and even the source code, so this pointless thread can come to an end? Obviously, if there's 3.5MB there, it is for *something*; the cygwin people didn't just fill up the library with a lot of no-ops. -- - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".