🚀 go-pugleaf

In article <1992Nov05.235245.11709@mixcom.com> calyx.corp <calyx.corp@mixcom.mixcom.com> writes:
>Is it is possible to distribute programs for profit that are 
>created with g++ and use the g++ libraries.  It is my understanding
>that this can be done if a copyright string is included in the 
>binary executable files.   It is also my understanding that this 
>can be done without requiring the release of source code that 
>we have created.  Is this correct?

Another item for the FAQ.

You don't have to release your source code.  But you need to go a
lot further than just putting a copyright string into the executable.

Compiling your code with a Gnu compiler does not affect its copyright;
it is still yours.  However, in order to ship code that links in a Gnu
library such as libg++ there are certain rules you must follow.  The
rules are described in the file COPYING.LIB that accompanies gcc
distributions; it is also included in the libg++ distribution.
See that file for the exact rules.  The agreement is called the
Library Gnu Public License or LGPL.

Here's the deal: let's say that you use some version of libg++,
completely unchanged, in your software, and you want to ship only
a binary form of your code.  You can do this, but there are several
special requirements.  If you want to use libg++ but ship only object
code for your code, you have to ship source for libg++ (or ensure
somehow that your customer already has the source for the exact
version you are using), and ship your application in linkable form.
You cannot forbid your customer from reverse-engineering or extending
your program by exploiting its linkable form.

Furthermore, if you modify libg++ itself, you must provide source
for your modifications (making a derived class does not count as
modifying the library -- that is "a work that uses the library").
--
Joe Buck	jbuck@ohm.berkeley.edu