Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Delivered-To: mailing list cygwin@sourceware.cygnus.com
Message-ID: <36E5C12D.5017@uni-duesseldorf.de>
Date: Wed, 10 Mar 1999 01:47:41 +0100
From: Stipe Tolj <tolj@uni-duesseldorf.de>
Reply-To: tolj@uni-duesseldorf.de
Organization: Department of Economical Computer Science, University of Cologne, 
              Germany
X-Mailer: Mozilla 3.01 (Win95; I)
MIME-Version: 1.0
To: DJ Delorie <dj@delorie.com>
CC: cygwin@sourceware.cygnus.com
Subject: Re: [ANN] Cygwin DEV survey
References: <36E2B26B.BEA9DC67@uni-duesseldorf.de> <199903071805.NAA13212@envy.delorie.com> <36E30CB6.1B5F@uni-duesseldorf.de> <199903080113.UAA15742@envy.delorie.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

DJ Delorie wrote:
> 
> The reason I specified full sources for all application is because
> when you build an application with cygwin, the resulting binary always
> includes sources from cygwin (namely, the startup code and import
> library stubs), so all applications thus compiled must be distributed
> under the terms of the GPL.

ok, this point is quite clear and should be accepted by anyone using
cygwin, me too. So I suppose we will compile a set of software which is
definitly distributed under the terms of GPL.

Now what about the xforms 0.881 cygwin pre-compiled port we have
provided to the xforms authors. They will only allow distribution of the
pre-compiled binary but not the patched cygwin port sources. This would
mean they would violate GPL since we have used cygwin b20.1 to compile
it?!

Regards,
Sttipe

-- 
Stipe Tolj <tolj@uni-duesseldorf.de>

Cygwin Porting Project -- "We build UNIX on top of Windows"
http://www.student.uni-koeln.de/cygwin

Department of Economical Computer Science        
University of Cologne, Germany



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

