From:	gfoot AT mc31 DOT merton DOT ox DOT ac DOT uk (George Foot)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Win32 support for DJGPP!!!!
Date:	21 Feb 1997 06:37:25 GMT
Organization:	Oxford University
Lines:	21
Message-ID:	<5ejfr5$rln@news.ox.ac.uk>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 970218130738 DOT 20213D-100000 AT is> <3309D5CA DOT 10F6E057 AT gnat DOT com> <330c8918 DOT 1063550 AT news DOT ping DOT be> <5eim9n$gos AT news DOT ox DOT ac DOT uk> <330CC3FC DOT 46BB5637 AT gnat DOT com>
NNTP-Posting-Host:	mc31.merton.ox.ac.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Douglas Rupp (rupp AT gnat DOT com) wrote:
: I'm afraid you've got this backwards.

Really? In what way? Could you elaborate? This is how I interpret the
licenses, anyway.

: George Foot wrote:
: > There are two separate licenses - the GPL (General Public License) and the
: > LGPL (Library General Public License). The LGPL requires you (among other
: > things) to release the full source code to any program which uses routines
: > from the library. As an example, libc is under GPL but libgpp is under LGPL.
: > Consequently, you can decide whether or not to release the source for any C
: > programs you write using libc, but if you write C++ programs using libgpp
: > you must release the source.
: > 
: > For information on this, type info gcc copying (this is the GPL) or info
: > libg++ copying (this is the LGPL).

-- 
George Foot <gfoot AT mc31 DOT merton DOT ox DOT ac DOT uk>
Merton College, Oxford.

- Raw text -