[GCC-XML]licensing

Fri, 1 Mar 2002 08:35:13 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1C0FC.01CF77F0
Content-Type: text/plain;
	charset="iso-8859-1"

Brad, 

I brought up this issue yesterday on the gcc mailling list, and in emails to
stallman and torvalds.

>>The rest of your application is
>>free to be under whatever license you choose.  It can process the output
>>from GCC-XML and do whatever it wants. 
It turns out that the processing of the output of gcc can be considered a
derived work of the gcc.
just because it is going through a network/file or memory does not make is
not derived.

2. I wrote to this topic to Richard Stallman.
Richard Stallman said to me in the question if the
data exchange over the network is not linking and
therefore not covered by the GPL 
"We have a different interpretation of the situation.
Connecting modules through sockets or pipes does not
necessarily mean they are separate programs. In simple
cases they are separate, but not when they exchange
complex data structures."

That would support the idea that all these are derived
works and fall under the GPL.

3. Linus Torvalds said :
>Feel free to consider this email (in its >entirety,
not snipped into pieces) as being >public, so if you
think you want to post it, go >ahead. 
>The GPL notion of "linking" is really nothing but >a
specific technical way of trying to define >"derived
work". 
>From a legal standpoint, technical issues have >some
validity, but in the end the _only_ thing >that
matters is whether it is derived or not. >Linking is
only one (strong) indicator that it is >indeed
derived. There are others. There are
>counter-indicators as well, of course, one of >them
being "previous work" (thus my willingness, >for
example, to have binary modules that were >basically
derived from SCO device drivers that >existed prior to
Linux - one of the original >impetuses for the module
interface). 
>And intent matters. 
>Linus

Hope that you find that interesting.
mike

-----Original Message-----
From: Brad King [mailto:brad.king@kitware.com]
Sent: Montag, 18. Februar 2002 18:01
To: petewon@netscape.net
Cc: gccxml@public.kitware.com
Subject: Re: [GCC-XML]licensing

> My first question is regarding licensing GCC-XML for use in a
> commercial software product. Are there any issues regarding
> distributing GCC-XML in binary form with commercial, closed-source
> software? The closed-source part would do some processing on the XML,
> show a GUI, allow data entry, etc. I primarily have the Windows
> platform in mind.
GCC-XML is licensed under the GPL simply because it is intended as a patch
for GCC.  This means that any application or library that distributes
binaries built from the code must also be under the GPL.  However, if your
application distributes GCC-XML as its own executable, then only THAT
PARTICULAR executable needs to be GPLed.  The rest of your application is
free to be under whatever license you choose.  It can process the output
from GCC-XML and do whatever it wants.  As long as no header or other code
from GCC or GCC-XML is actually compiled into the application's libraries
or executables, there are no license restrictions.

You probably want to do this:

1.)  Build the GCC-XML exectuable separately from the rest of your
application.  Include this executable in the distribution (don't forget
the cygwin DLL on windows).  Use only your own code to parse the output.

2.)  In your documentation, include a copy of the GPL and give links to
the GCC and GCC-XML homepages.

I think that will be sufficient to satisfy the license.

> Also, I was wondering if you need any help on this project. This isn't
> some sort of bribe, I'm genuinely interested in helping :)
Once I have finished the initial re-write with the new output format, I
will probably be asking the list for help on additional features.  
Thanks.

-Brad

_______________________________________________
gccxml mailing list
gccxml@public.kitware.com
http://public.kitware.com/mailman/listinfo/gccxml

------_=_NextPart_001_01C1C0FC.01CF77F0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: [GCC-XML]licensing</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Brad, </FONT>
</P>

<P><FONT SIZE=2>I brought up this issue yesterday on the gcc mailling list, and in emails to stallman and torvalds.</FONT>
</P>

&gt;&gt;The rest of your application is
 &gt;&gt;free to be under whatever license you choose.&nbsp; It can process the output
 &gt;&gt;from GCC-XML and do whatever it wants. 
 It turns out that the processing of the output of gcc can be considered a derived work of the gcc.
 just because it is going through a network/file or memory does not make is not derived.

2. I wrote to this topic to Richard Stallman.
 Richard Stallman said to me in the question if the
 data exchange over the network is not linking and
 therefore not covered by the GPL 
 &quot;We have a different interpretation of the situation.
 Connecting modules through sockets or pipes does not
 necessarily mean they are separate programs. In simple
 cases they are separate, but not when they exchange
 complex data structures.&quot;

<P><FONT SIZE=2>That would support the idea that all these are derived</FONT>
<BR><FONT SIZE=2>works and fall under the GPL.</FONT>
</P>

3. Linus Torvalds said :
 &gt;Feel free to consider this email (in its &gt;entirety,
 not snipped into pieces) as being &gt;public, so if you
 think you want to post it, go &gt;ahead. 
 &gt;The GPL notion of &quot;linking&quot; is really nothing but &gt;a
 specific technical way of trying to define &gt;&quot;derived
 work&quot;. 
 &gt;From a legal standpoint, technical issues have &gt;some
 validity, but in the end the _only_ thing &gt;that
 matters is whether it is derived or not. &gt;Linking is
 only one (strong) indicator that it is &gt;indeed
 derived. There are others. There are
 &gt;counter-indicators as well, of course, one of &gt;them
 being &quot;previous work&quot; (thus my willingness, &gt;for
 example, to have binary modules that were &gt;basically
 derived from SCO device drivers that &gt;existed prior to
 Linux - one of the original &gt;impetuses for the module
 interface). 
 &gt;And intent matters. 
 &gt;Linus

<P><FONT SIZE=2>Hope that you find that interesting.</FONT>
<BR><FONT SIZE=2>mike</FONT>
</P>

-----Original Message-----
 From: Brad King [<A HREF="mailto:brad.king@kitware.com">mailto:brad.king@kitware.com</A>]
 Sent: Montag, 18. Februar 2002 18:01
 To: petewon@netscape.net
 Cc: gccxml@public.kitware.com
 Subject: Re: [GCC-XML]licensing

&gt; My first question is regarding licensing GCC-XML for use in a
 &gt; commercial software product. Are there any issues regarding
 &gt; distributing GCC-XML in binary form with commercial, closed-source
 &gt; software? The closed-source part would do some processing on the XML,
 &gt; show a GUI, allow data entry, etc. I primarily have the Windows
 &gt; platform in mind.
 GCC-XML is licensed under the GPL simply because it is intended as a patch
 for GCC.&nbsp; This means that any application or library that distributes
 binaries built from the code must also be under the GPL.&nbsp; However, if your
 application distributes GCC-XML as its own executable, then only THAT
 PARTICULAR executable needs to be GPLed.&nbsp; The rest of your application is
 free to be under whatever license you choose.&nbsp; It can process the output
 from GCC-XML and do whatever it wants.&nbsp; As long as no header or other code
 from GCC or GCC-XML is actually compiled into the application's libraries
 or executables, there are no license restrictions.

<P><FONT SIZE=2>You probably want to do this:</FONT>
</P>

<P><FONT SIZE=2>1.)&nbsp; Build the GCC-XML exectuable separately from the rest of your</FONT>
<BR><FONT SIZE=2>application.&nbsp; Include this executable in the distribution (don't forget</FONT>
<BR><FONT SIZE=2>the cygwin DLL on windows).&nbsp; Use only your own code to parse the output.</FONT>
</P>

<P><FONT SIZE=2>2.)&nbsp; In your documentation, include a copy of the GPL and give links to</FONT>
<BR><FONT SIZE=2>the GCC and GCC-XML homepages.</FONT>
</P>

<P><FONT SIZE=2>I think that will be sufficient to satisfy the license.</FONT>
</P>

&gt; Also, I was wondering if you need any help on this project. This isn't
 &gt; some sort of bribe, I'm genuinely interested in helping :)
 Once I have finished the initial re-write with the new output format, I
 will probably be asking the list for help on additional features.&nbsp; 
 Thanks.

<P><FONT SIZE=2>-Brad</FONT>
</P>

<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>gccxml mailing list</FONT>
<BR><FONT SIZE=2>gccxml@public.kitware.com</FONT>
<BR><FONT SIZE=2><A HREF="http://public.kitware.com/mailman/listinfo/gccxml" TARGET="_blank">http://public.kitware.com/mailman/listinfo/gccxml</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1C0FC.01CF77F0--