Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 27 Jan 2004 14:55:31 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem with DLLs and processes
Message-ID: <20040127195531.GA17793@redhat.com>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <OF081A6C4B DOT E9E7AC69-ON80256E28 DOT 00398068 AT db DOT com> <NUTMEGVdXjhGPLqmK6L0000002f AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040127103952 DOT 0383f470 AT 127 DOT 0 DOT 0 DOT 1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.0.1.1.0.20040127103952.0383f470@127.0.0.1>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

On Tue, Jan 27, 2004 at 10:48:16AM -0500, Larry Hall wrote:
>Actually, the recommended approach is to distribute your program that 
>depends on Cygwin and then point to cygwin.com's setup to install the
>Cygwin package (and anything else needed/wanted).  Obviously, this could
>be automated too.
>
>>  This has a slight danger, that the version with your exe might clash with
>>an existing version of cygwin dll already on the computer.  To avoid this,
>>you can install your exe and the cygwin dll into a directory of their own.
>>Then you create a file in that directory that has the exact same name as
>>your exe with ".local" appended.  This means that when your .exe runs, it
>>will look in the same directory for its dlls before it looks in the windows
>>system dir.  That way, your exe gets the version of the dll it expects, but
>>none of the existing software on the machine you install will interact with
>>it.  Google for "side-by-side DLLs" if you want to know more.
>
>
>Actually, this will still cause a clash for the Cygwin.  But since 
>Cygwin DLLs are backward compatible, the recommended approach, which I 
>mentioned above, of distributing the Cygwin DLL will avoid any type of 
>clash.

Right.  You can't have multiple cygwin's operating on the same computer.

Also, lets not forget that any code you link against cygwin will be GPLed
and if you distribute some form of the cygwin DLL you'll need to also
distribute sources of the DLL under the GPL.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/