This is the mail archive of the email@example.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Does GPL apply without Cygwin stub? [long and off-topic] (was Re: [ANN] Cygwin DEV survey)
- To: firstname.lastname@example.org
- Subject: Re: Does GPL apply without Cygwin stub? [long and off-topic] (was Re: [ANN] Cygwin DEV survey)
- From: DJ Delorie <email@example.com>
- Date: Mon, 8 Mar 1999 18:01:25 -0500
- CC: Ssiddiqi@InspirePharm.Com, firstname.lastname@example.org
- Delivered-To: email@example.com
- Delivered-To: mailing list firstname.lastname@example.org
- In-reply-to: <199903082259.RAA18063@delorie.com> (email@example.com)
- Mailing-List: contact firstname.lastname@example.org; run by ezmlm
- References: <008f01be69b6$f4fa6ed0$29acdfd0@InspirePharm.Com> <199903082247.RAA11818@envy.delorie.com> <199903082259.RAA18063@delorie.com>
- Sender: email@example.com
> Ergo, if you buy such a product, you MUST NOT run any other software that
> loads the cygwin1.dll, because either you would be making their product
> load the GPL'd dll or your GPL software would be loading the license
> restricted dll.
Since Windows checks the directory the executable runs from before the
PATH, this shouldn't be a problem if the dll is stored with the
executable and you manage your path properly. Yes, I know it doesn't
always work that way. If you have two cygwin1.dlls in your PATH and
they're incompatible, you might have other problems anyway.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org