From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,41b26d4b4b1c530a
X-Google-Attributes: gid103376,public
From: lance@eco.twg.com (Lance Kibblewhite)
Subject: Re: Gnat 3.09 NT - Legal issues
Date: 1997/02/10
Message-ID: <32ff443d.1365753@library.airnews.net>#1/1
X-Deja-AN: 217815549
references: <01bc0fc4$c6d53740$829d6482@joy.ericsson.se>
 <dewar.855492299@merv>
content-type: text/plain; charset=us-ascii
organization: Attachmate
mime-version: 1.0
reply-to: lance@eco.twg.com
newsgroups: comp.lang.ada
Date: 1997-02-10T00:00:00+00:00
List-Id: <comp.lang.ada>


dewar@merv.cs.nyu.edu (Robert Dewar) wrote:

>jonas asks
>
><<Can I be sure that ANY program I produce with Gnat 3.09 for NT/Win95 will
>not contain parts governed by the rules of LGPL. The Gnat license states
>that the inclusion of any library code does not fall under the terms of
>LGPL, but how do I know that there has not been included any code from
>the libraries provided by Cygnus (Gnu) in my application.
>>>
>
>Well someone always likes to raise FUD on this issue from time to time :-)
>There are no problems in this regard. No LGPL'ed or otherwise problematic
>code is included in your generated executables. 
>
>We will be happy to explain this further to any of our customers who might
>be concerned -- please send mail to sales@gnat.com if you have further
>questions.

Yes, but what about the Cygnus libraries?

Their Web page contains the following paragraph:

>How is this software copyrighted?
>
>Like all GNU software, the source code and modifications developed
>by Cygnus Support for this project are under the GNU General Public
>License (GPL). As of beta 17, library code in the cygwin.dll (which
>is embedded in your program if you use the gnu-win32 tools) is now
>under the GNU General Public License which means that unless people
>figure out a way of not linking against libcygwin.a (which is needed
>to make libc and libm work right now), the program most likely also
>has to become free software under the GPL. If in doubt, check the
>relevant files in the code for the copyright notices.

Which is fine.

However, over the weekend, I receieved a mail on the on the gnu-win32
mailing list which indicated that Cygnus intend to somehow modify this
policy to require some form of licensing for what they called
'proprietary' applications.

I don't have a copy with me at the moment, and I'm not sure if I saved
it at home or not.  If I do have it, I'll post it as a followup.

-- Lance.