Date:	Tue, 11 May 1999 22:32:45 -0400 (EDT)
Message-Id:	<199905120232.WAA00176@indy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp AT delorie DOT com
In-reply-to:	<7hamt5$16a$1@news.ececs.uc.edu> (mgwise@seidata.com)
Subject:	Re: The GNU public license
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> So I'll ask all of you...what do I need to include in my
> distributions if I compile a program with djgpp and allegro, if I
> haven't modified any of the sources and I only link in libc.a (an
> perhaps libstc++.a (i think that's the right one, but I'm not sure I
> actually linked it in or not...)

libc.a - if it's the one you got from an official djgpp distribution,
this alone doesn't mean you have to do anything.  Quake was built with
djgpp, and it didn't come with sources at all.  Note - this only
applies to an *unmodified* libc.a.  If you change it, the full GNU GPL
applies and you must provide *full sources* with any binaries.

libstdc++.a - if your application is built with gcc (which it would
be, since djgpp uses gcc), this alone doesn't mean you have to do
anything.  Note: libg++.a is NOT like this, but you shouldn't really
be using it anyway, as it's obsolete.

liballeg.a - This doesn't mean you have to do anything, but they
*request* that you give a gift to the allegro community, such as
improvements to allegro, releasing your sources, funding development,
etc.

So, basically, if you're using everything "out of the box", you
shouldn't have to give any sources away with your binaries.

- Raw text -