Mail Archives: cygwin/1999/07/18/10:22:14
This has been discussed in length. Search the archives.
--- Geoff Appleby <geoff AT topic DOT com DOT au> wrote:
> 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
>
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -