This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: License question (Distribution of cygwin1.dll
- From: "Buchbinder, Barry (NIH/NIAID) [E]" <barry dot buchbinder at nih dot gov>
- To: patrick schmidt <msc dot patrick dot schmidt at gmail dot com>, "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Mon, 7 May 2018 14:43:06 +0000
- Subject: RE: License question (Distribution of cygwin1.dll
- References: <CALw8M6BNPfkq6_9yvw78vpbtpjQPjAt8UgbL-NDwQ3yn0Zp=Pw@mail.gmail.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
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 code of this product. We do not modify cygwin1.dll,
>just distribute and the iPerf3.exe is only called as an seperate
>process.
>
>Does cygwin license allow this and if not is there anyone you can
>contact for other licensing options which do not force you to give out
>the source code?
See page and LGPL links: https://cygwin.com/licensing.html
FAQ: https://cygwin.com/faq.html#faq.using.bundling-cygwin
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple