From:	shankar AT chromatic DOT com (Shankar Unni)
Subject:	Re: cygwin.dll
16 Jan 1997 21:22:36 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<32DEE362.4CB06141.cygnus.gnu-win32@chromatic.com>
References:	<1 DOT 5 DOT 4 DOT 16 DOT 19970116123433 DOT 252f4572 AT scooter DOT gcal DOT ac DOT uk>
Mime-Version:	1.0
X-Mailer:	Mozilla 3.01Gold (X11; I; Linux 2.0.18 i586)
Original-To:	"M.Carter" <M DOT Carter AT gcal DOT ac DOT uk>
Original-CC:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

M.Carter wrote:

> I'd like to mention that I used Visual C++ to write a simple 'hello
> world'
program for Windows 95. It was 17k long. I found that the
> machine transported to another machine running Windows 95 without
> the need for distributing a dll, or any other paraphenalia.

On the other hand, if you use VC++ 4.2, and link a program against any
of their new C++ libraries, and want to transport *that* to another
machine, you do have to copy over the appropriate DLL: they explicitly
ask you to do so in the documentation. So it's not as clear-cut as you
say.  You only luck out if you use only libraries that are shipped as
part of the base Win95. You can't even depend on a new library that
ships standard as part of OSR1 or OSR2, because not all your users may
have it.

The thing to remember about Windows, is that software developers are
responsible for hiding all the crud from the user's eyes; that's the
entire philosophy of Win95. It's not that there's no crud - heavens,
there's tons of it.

So yeah: you want to distribute applications to a different machine,
ship a copy of cygwin.dll along with your app, just like you'd do with
VC++ 4.2-compiled apps..

-- 
Shankar Unni                                  shankar AT chromatic DOT com
Chromatic Research                            (408) 752-9488
-
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 -