Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<80575AFA5F0DD31197CE00805F650D7602CF71@wilber.adroit.com>
From:	"Robinow, David" <drobinow AT dayton DOT adroit DOT com>
To:	Corinna Vinschen <cygwin AT cygwin DOT com>
Subject:	RE: CYGWIN1.DLL
Date:	Tue, 17 Jul 2001 12:38:23 -0400
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2650.21)

> From: Eric M. Monsler [mailto:emonsler AT beamreachnetworks DOT com]
> Subject: Re: CYGWIN1.DLL
> One example:  I've written a small utility to pass a specialized
> message-format between UDP and the PC's serial port.  Its distribution
> is entirely within our company.  
> 
> I currently have both the application and the .dll checked in 
> to our CM
> tools under "utils", so that folks can run it without having cygwin
> installed on their PC.  
> 
> Only a few of us have cygwin installed, but there is a potential
> conflict problem with having two cygwin1.dll files, if the CM'd version
> lags or leads the version on any given developer's desktop.  Thus far,
> the cygwin users here are a) mostly knowledgeable enough to deal with
> the issue, and b) few enough that I can support them if the conflict
> ocurred.
  It should be possible to modify 'setup' to handle this.  I anticipate
needing something like this myself (somewhere between "soon" and
"some day".

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -