public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Buchbinder, Barry (NIH/NIAID) [E]" <barry.buchbinder@nih.gov>
To: patrick schmidt <msc.patrick.schmidt@gmail.com>,
	"cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: RE: License question (Distribution of cygwin1.dll
Date: Mon, 07 May 2018 17:54:00 -0000	[thread overview]
Message-ID: <BYAPR09MB282377A95D94A9EEA11863249B9B0@BYAPR09MB2823.namprd09.prod.outlook.com> (raw)
In-Reply-To: <CALw8M6BNPfkq6_9yvw78vpbtpjQPjAt8UgbL-NDwQ3yn0Zp=Pw@mail.gmail.com>

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


      reply	other threads:[~2018-05-07 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 15:21 patrick schmidt
2018-05-07 17:54 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BYAPR09MB282377A95D94A9EEA11863249B9B0@BYAPR09MB2823.namprd09.prod.outlook.com \
    --to=barry.buchbinder@nih.gov \
    --cc=cygwin@cygwin.com \
    --cc=msc.patrick.schmidt@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).