public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Greg Freemyer <greg.freemyer@gmail.com>
To: cygwin@cygwin.com
Subject: Re: compile ncurses "hello world" to run independent of cygwin?
Date: Mon, 02 Nov 2015 15:14:00 -0000	[thread overview]
Message-ID: <CAGpXXZKySmMk3tcHwW_hBnJT+9abzMA_SjRk4McF0PLwHHqjxA@mail.gmail.com> (raw)
In-Reply-To: <56375B94.4060107@gmail.com>

On Mon, Nov 2, 2015 at 7:48 AM, cyg Simple <cygsimple@gmail.com> wrote:
> On 11/1/2015 11:09 PM, Darik Horn wrote:
>>
>> Unless there is a specific reason to cross through Cygwin, it could be
>> easier to use the native MinGW environment directly:
>>
>> * http://www.mingw.org/wiki/Getting_Started
>>
>
> Poppycock! There is no reason that the user couldn't use Cygwin as the
> one and only system to build native binaries.

I'm relatively new to this mailing list.  Apologies if this is well
covered ground....

The last time I checked (a few years ago), my understanding was the
cygwin dll's were licensed such that any programs using them had to be
GPL (or equivalent).

Is that wrong?

If so, anyone wanting to write a commercial tool has to avoid the
cygwin's core dll's.

Does using mingw do so?

Thanks
Greg

--
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:[~2015-11-02 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02  3:04 Daniel Goldman
2015-11-02  4:09 ` Darik Horn
2015-11-02 12:48   ` cyg Simple
2015-11-02 15:14     ` Greg Freemyer [this message]
2015-11-02 15:34       ` Darik Horn
2015-11-02 15:49       ` Corinna Vinschen
2015-11-02 12:42 ` cyg Simple

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=CAGpXXZKySmMk3tcHwW_hBnJT+9abzMA_SjRk4McF0PLwHHqjxA@mail.gmail.com \
    --to=greg.freemyer@gmail.com \
    --cc=cygwin@cygwin.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).