Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<37917BF7.B7FFFB1E@topic.com.au>
Date:	Sun, 18 Jul 1999 17:02:15 +1000
From:	Geoff Appleby <geoff AT topic DOT com DOT au>
X-Mailer:	Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Copyright restrictions on cygwin

Hello again :)

This is an easy question - no really!

I saw some discussion in the last few days about licensing agreements
etc for code developedon Cygwin.
I'm not an expert at reading license agreements, they jsut confuse me,
so if someone has a definitive answer,
I'd appreciate it.

I'm using Cygwin B20.1.
I've written an application that is entirely my own code.
I've compiled on NT using cygwin, and the objdump of the executable
contains
2 entries.  cygwin1.dll and kernel32.dll.
Obviously, i don't need to worry about kernel32.
To supply this application to other people, I need to provide them with
cygwin1.dll.

So far I'm even boring myself :)

Now, if this application is sold to a client,  what exactly must i
provide along
with the cygwin1.dll?  By this, i mean as far as the licensing goes - is
an acknowledgement enough,
a copy of the cygwin license statement, what?

I'm not going to bother asking what happens if i then go and statically
link in some of libwww in as well,
as i  know this isn't the place :)

Thanks.
Geoff Appleby


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -