This is the mail archive of the
mailing list for the Cygwin project.
RE: Licensing question
- To: "'Jim dot Fairchild at IndSys dot ge dot com'" <Jim dot Fairchild at IndSys dot ge dot com>, cygwin at sourceware dot cygnus dot com
- Subject: RE: Licensing question
- From: Erik Hensema <erik dot hensema at group2000 dot nl>
- Date: Thu, 21 Oct 1999 08:48:55 +0200
> -----Original Message-----
> From: Jim.Fairchild@IndSys.ge.com [mailto:Jim.Fairchild@IndSys.ge.com]
> I have a question regarding the statement, "if you intend to
> port a commercial
> (non-GPL'd) application using Cygwin, you will need the
> commercial license to
> Cygwin that comes with the supported native Win32 GNUPro
> product". What
> licensing restrictions apply if you plan on using the Unix
> utilities only, and
> will not be developing applications that use the cygwin? The
> Unix utilities
> would be used in a commercial application to enable the
> customer to transition
> from a UNIX system to a Windows NT system.
> Thanks for your help.
Well, I don't think you need a commercial license. You don't link anything
with GPL code. You don't modify any GPL code (and if you did, you could
still supply the source). Just like it's legal to sell Linux for big bucks,
you can sell Cygwin at any cost you like.
Generally, whats not allowed, is linking non-open-source code with GPL code.
However, this isn't a matter of source code at all.
Now a commercial application using binaries compiled from GPL source: that's
very common. Many, many softwarehouses develop using GCC and sell
closed-source software. Many commercial websites run Linux/Apache/MySQL. Non
problem at all.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org