delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/07/16/11:24:36

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3E2D8043936AD611AF7D00508B5E9F4B48B482@server3.mobilecom.com>
From: Cary Lewis <clewis AT mobilecom DOT com>
To: cygwin AT cygwin DOT com
Subject: License question about Cygwin
Date: Wed, 16 Jul 2003 11:23:43 -0400
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Jul 2003 15:33:38.0032 (UTC) FILETIME=[A07B9700:01C34BAF]

As the Cygwin.dll is licensed under GPL, any "Program" that links to it must
be released under GPL as well.

My question is, what if the "Program" also links to proprietary .dlls that
are authored by someone else. That source can not be published (I don't even
have access to it). Furthermore these .dlls are not freely available.

Does that mean that even if I publish all of my source code, I would still
be violating the GPL because I couldn't publish the source code to the
proprietary libraries.

Thanks for any help.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019