From: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Subject: Re: Why is cygwin.dll?
17 Jan 1997 11:27:53 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <009AE7B8.68408AA0.7387.cygnus.gnu-win32@ifk20.mach.uni-karlsruhe.de>
Original-To: grantl AT deerinet DOT nb DOT ca
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:

: Maybe if you could get it ported to Visual C++, however when talking about
: cygwin.dll, as mentioned in Jim Balter's reply to the same thread, if you
: compile this on Visual C++ it would be using DOS's file system and syscalls
: etc.. yet under cygwin.dll for file access it would need all the extra code
: which cygwin.dll adds to mimic the  Unix subsystems. This would no doubt be
: a rather large amount, and if just making something like grep by itself
: mostly be unnecessary, assuming you just want want grep on win32.

No wonder that msvcrt*.dll are only about 10% of cygwin.dll!

Who was it wanting a standalone executable for easier distribution?
I remember when building with msvc and copying the executable to another
system, it first failed because msvcrt*.dll is not by default on NT!
Dunno if you can produce a purely static thing... (except kernel32 etc 8-)


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".