Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Wed, 20 Oct 1999 16:04:19 -0400 To: Jim DOT Fairchild AT IndSys DOT ge DOT com Cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Licensing question Message-ID: <19991020160419.A1286@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: Jim DOT Fairchild AT IndSys DOT ge DOT com, cygwin AT sourceware DOT cygnus DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Jim.Fairchild@IndSys.ge.com on Wed, Oct 20, 1999 at 01:48:55PM -0500 On Wed, Oct 20, 1999 at 01:48:55PM -0500, Jim DOT Fairchild AT IndSys DOT ge DOT com wrote: >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? Actually, the "UNIX utilities" use Cygwin. Since most of them are distributed under the GPL, you will need to provide the sources for the binaries that you are distributing. This would include things like make, gcc, gdb, awk, and cygwin1.dll itself. FYI, unless you are compiling programs using gcc with the -mno-cygwin option, your binaries are using cygwin. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com