patrick schmidt sent the following at Monday, May 07, 2018 10:28 AM
>
>I want to use iPerf3.exe in an commercial projekt. iPerf uses the MIT
>License but needs cygwin1.dll in order to function correctly.
>
>I need to distribute iperf3.exe in our commercial software, but we cant
>release the source
Hello dear Cygwin community,
I want to use iPerf3.exe in an commercial projekt. iPerf uses the MIT
License but needs cygwin1.dll in order to function correctly.
I need to distribute iperf3.exe in our commercial software, but we cant
release the source code of this product. We do not modify cygwin
On Wed, Jul 16, 2003 at 02:48:14PM -0400, Tillman, James wrote:
>
>
>> -Original Message-
>> From: Elfyn McBratney [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, July 16, 2003 11:43 AM
>> To: [EMAIL PROTECTED]
>> Cc: Cary Lewis
>> Subject: Re: Licen
On Wed, Jul 16, 2003 at 04:46:24PM -0400, Bill C Riemers wrote:
>The answer isn't quite that simple. The correct answer, is that it depends
>on the details of what you are doing. I could go into more details, but
>this topic has already been moderated once. It would be inappropriate for
>me to d
> > As the Cygwin.dll is licensed under GPL, any "Program" that links to it
must
> > be released under GPL as well.
>
> Under section 10 of the GPL, if the "program" is OSD compatible then the
> "program" is not auto-GPL'd.
Actually section 10 of the GPL just states the following:
> 10. If you wi
> -Original Message-
> From: Elfyn McBratney [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 16, 2003 11:43 AM
> To: [EMAIL PROTECTED]
> Cc: Cary Lewis
> Subject: Re: License question about Cygwin
>
>
> On Wed, 16 Jul 2003, Elfyn McBratney wrote:
>
ownership for.)
Bill
- Original Message -
From: "Cary Lewis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 16, 2003 11:23 AM
Subject: License question about Cygwin
> As the Cygwin.dll i
On Wed, 16 Jul 2003, Elfyn McBratney wrote:
> On Wed, 16 Jul 2003, Cary Lewis wrote:
>
> > As the Cygwin.dll is licensed under GPL, any "Program" that links to it must
> > be released under GPL as well.
>
> Under section 10 of the GPL, if the "program" is OSD compatible then the
> "program" is not
On Wed, 16 Jul 2003, Cary Lewis wrote:
> As the Cygwin.dll is licensed under GPL, any "Program" that links to it must
> be released under GPL as well.
Under section 10 of the GPL, if the "program" is OSD compatible then the
"program" is not auto-GPL'd.
> My question is, what if the "Program" als
As the Cygwin.dll is licensed under GPL, any "Program" that links to it must
be released under GPL as well.
My question is, what if the "Program" also links to proprietary .dlls that
are authored by someone else. That source can not be published (I don't even
have access to it). Furthermore these
: [EMAIL PROTECTED]
Subject: Re: License question
On Mon, Mar 10, 2003 at 10:04:01PM -0800, Pete Nordquist wrote:
>Thank you, Christopher, for your quick reply. I didn't mean to imply
>that every binary produced by gcc is GPLed.
I'm not sure how you could take your assertion any othe
On Mon, Mar 10, 2003 at 10:04:01PM -0800, Pete Nordquist wrote:
>Thank you, Christopher, for your quick reply. I didn't mean to imply
>that every binary produced by gcc is GPLed.
I'm not sure how you could take your assertion any other way unless you
think there is something special about cygwin
ter Science
Southern Oregon University
[EMAIL PROTECTED]
541/552-6148
-Original Message-
From: Christopher Faylor [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 09, 2003 8:43 PM
To: [EMAIL PROTECTED]
Subject: Re: License question
On Sun, Mar 09, 2003 at 06:47:44PM -0800, Pete Nordquis
On Sun, Mar 09, 2003 at 06:47:44PM -0800, Pete Nordquist wrote:
>I read the following on
>http://sources.redhat.com/cygwin/faq/faq_1.html#SEC4
>
>In particular, if you intend to port a proprietary (non-GPL'd)
>application using Cygwin, you will need the proprietary-use license for
>the Cygwin libra
I read the following on
http://sources.redhat.com/cygwin/faq/faq_1.html#SEC4
In particular, if you intend to port a proprietary (non-GPL'd)
application using Cygwin, you will need the proprietary-use license for
the Cygwin library. This is available for purchase; please visit
http://www.redhat.com
On Mon, Jan 07, 2002 at 04:58:49PM -0500, Christopher Faylor wrote:
> On Mon, Jan 07, 2002 at 12:43:14PM -0600, Dave Dykstra wrote:
> >Hi,
> >
> >I have a few questions about Cygwin licensing, and the last one I think is
> >kind of tricky.
> >
> >I run a software distribution system in Lucent that
On Mon, Jan 07, 2002 at 12:43:14PM -0600, Dave Dykstra wrote:
>Hi,
>
>I have a few questions about Cygwin licensing, and the last one I think is
>kind of tricky.
>
>I run a software distribution system in Lucent that automatically
>distributes hundreds of tools, mostly open source tools but also s
Hi,
I have a few questions about Cygwin licensing, and the last one I think is
kind of tricky.
I run a software distribution system in Lucent that automatically
distributes hundreds of tools, mostly open source tools but also some
internal proprietary tools. The system includes a remote-compile
18 matches
Mail list logo
