This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GNU Compiler license
- To: Ken McLeod <k_mcleod at atinucleus dot com>
- Subject: Re: GNU Compiler license
- From: Sam TH <sam at uchicago dot edu>
- Date: Wed, 6 Dec 2000 10:25:24 -0600
- Cc: gcc at gcc dot gnu dot org
- References: <003b01c05f9b$c5f91960$54a8efd0@atinucleus.com>
On Wed, Dec 06, 2000 at 09:46:59AM -0600, Ken McLeod wrote:
> Hello,
>
> First, if we do not integrate the GNU compilers with our IDE, do we still need a license to distribute the GNU compiler on our CD with our products?
>
You already have a license to distribute GCC, that is, the GPL. If
you do distribute GCC as a standalone product, you merely need to make
an offer to distribute the source to GCC, which is just a matter of
mirroring the gcc sources on your website.
> Once we do integrate the GNU compiler into our IDE, can we distribute it with our IDE without being forced by the GPL to make our IDE source code public?
>
That depends on the kind of integration. If you simply call the
compiler on the source, then you can do whatever you want with your
IDE. If you link, in the library sense, your IDE to GCC, then you may
be required to license your IDE under the GPL. However, as Robert
mentioned, this shouldn't be neccessary for an IDE.
> I understand any changes we make to the GNU compiler must remain public, but if we integrate the GNU compiler into our IDE, where does the public GNU software stop and our private software start?
>
Again, this depends on the method of integration.
And, of course, I don't actually know anything about your particular
situation, so for real opinions, the best thing to do is get the
advice of your lawyer.
sam th
sam@uchicago.edu
http://www.abisource.com/~sam/
GnuPG Key:
http://www.abisource.com/~sam/key
PGP signature