Date:	Mon, 26 Feb 1996 08:14:13 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	teemut AT megabaud DOT fi
Cc:	djgpp AT delorie DOT com
Subject:	Re: Compiling without libgcc.a
In-Reply-To:	<4gk3r5$95h@news.mdata.fi>
Message-Id:	<Pine.SUN.3.91.960226080813.6409E-100000@is>
Mime-Version:	1.0

On 23 Feb 1996, it was written:

> I'm currently writing a freeware game with djgpp v.2.0.
> However I don't want that my program is under GNU licence, since
> I don't want do share it's sources. How can I be sure the executable
> doesn't use any libraries that are under that licence?
> 
> Curretly I compile program like this:
> 
> gcc -c -o myprog.o myprog.cpp -O2 -Wall -m386 -fpack-struct -save-temps
> gcc -c -o myprog2.o myprog2.cpp -O2 -Wall -m386 -fpack-struct -save-temps  
> gcc -o myprog.cof myprog2.o myprog.o -lemu -save-temps
> stubify myprog

The above means that you don't link in the libgpp.a C++ classes library.  
That is the only library that puts your program under any of the GNU 
licences.  If you don't use it, you can do whatever you like with your 
program.  The DJGPP FAQ (faq200b.zip from the same place you get DJGPP) 
explains this with some more details in section 19.1.

> I don't use any C++ iostream funktions, but my own code 
> uses a lot of classes, new, delete and other C++ spesific 

Even if you did use libiostream, your program wouldn't be under GNU LGPL, 
because that library doesn't impose it.  See the FAQ for details.

- Raw text -