From:	s2172184 AT cse DOT unsw DOT edu DOT au ("Ben Constable")
Subject:	Re: Why is cygwin.dll?
17 Jan 1997 10:19:39 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<970117165210.2541.cygnus.gnu-win32@cse.unsw.edu.au>
Mime-Version:	1.0
Original-To:	"Grant Leslie" <grantl AT deerinet DOT nb DOT ca>, "GNU-WIN32" <gnu-win32 AT cygnus DOT com>
X-MSMail-Priority:	Normal
X-Priority:	3
X-Mailer:	Microsoft Internet Mail 4.70.1155
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

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

You would not be using the DOS file system. You would be using the NT one.
And you end uip using the same file system anyway, because cygwin.dll uses
the NT file system and syscalls that visual C++ apps use. And I think your
final point is the one that a lot of people want to make. A stand alone
executable for a simple program would not break 100k, and would therefore
be easier to give to somebody who did not have gnu-win32.

Ben Constable
s2172184 AT cse DOT unsw DOT edu DOT au

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