FSF GCC merge 02/23/03
[official-gcc.git] / libstdc++-v3 / docs / html / 17_intro / license.html
bloba0a2c9135eaebe332fdd7cad47651d95e28fcf3d
1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE html
3 PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
4 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
6 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
7 <head>
8 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
9 <meta name="AUTHOR" content="pme@gcc.gnu.org (Phil Edwards)" />
10 <meta name="KEYWORDS" content="libstdc++, license, licence" />
11 <meta name="DESCRIPTION" content="Copying restrictions for libstdc++." />
12 <meta name="GENERATOR" content="vi and eight fingers" />
13 <title>libstdc++-v3 copying</title>
14 <link rel="StyleSheet" href="../lib3styles.css" />
15 </head>
16 <body>
18 <h1 class="centered"><a name="top">Licenses for the Library</a></h1>
20 <p>There are two licenses affecting GNU libstdc++-v3: one for the code, and
21 one for the documentation. Here we will describe both of them, and try
22 to answer some of the widespread questions. If you have more questions,
23 ask the FSF or the
24 <a href="http://gcc.gnu.org/lists.html">gcc mailing list</a>; the person
25 writing this page is a programmer, not a lawyer.
26 </p>
28 <hr />
30 <h2>The Code: Runtime GPL</h2>
32 <p>The source code of libstdc++-v3 is distributed under version 2 of the
33 <a href="COPYING">GNU General Public License</a>, with the so-called
34 &quot;runtime exception,&quot; as follows (or see any header or
35 implementation file):
36 </p>
37 <pre>
38 As a special exception, you may use this file as part of a free software
39 library without restriction. Specifically, if other files instantiate
40 templates or use macros or inline functions from this file, or you compile
41 this file and link it with other files to produce an executable, this
42 file does not by itself cause the resulting executable to be covered by
43 the GNU General Public License. This exception does not however
44 invalidate any other reasons why the executable file might be covered by
45 the GNU General Public License.
46 </pre>
48 <p>Hopefully that text is self-explanatory. If it isn't, you need to speak
49 to your lawyer, or the Free Software Foundation.
50 </p>
52 <!-- Most of the Q&A's are based on, paraphrased from, and outright stolen
53 from this thread:
54 http://gcc.gnu.org/ml/libstdc++/2000-q2/subjects.html#00050
55 -->
56 <p><strong>Q: So any program which uses libstdc++ falls under the GPL?</strong>
57 <br />A: <strong>No.</strong> The special exception permits use of the
58 library in proprietary applications.
59 </p>
61 <p><strong>Q: How is that different from the GNU {Lesser,Library}
62 GPL?</strong>
63 <!-- Quoting Jason Merrill from the thread above: -->
64 <br />A: The LGPL requires that users be able to replace the LGPL code with a
65 modified version; this is trivial if the library in question is a C
66 shared library. But there's no way to make that work with C++, where
67 much of the library consists of inline functions and templates, which
68 are expanded inside the code that uses the library. So to allow people
69 to replace the library code, someone using the library would have to
70 distribute their own source, rendering the LGPL equivalent to the GPL.
71 </p>
73 <p><strong>Q: I see. So, what restrictions <em>are</em> there on
74 programs that use the library?</strong>
75 <br />A: None. We encourage such programs to be released as open source,
76 but we won't punish you or sue you if you choose otherwise.
77 </p>
79 <hr />
81 <h2>The Docs: FDL</h2>
83 <p>The documentation shipped with the library and made available over the
84 web, including the pages generated from source comments, are copyrighted
85 by the Free Software Foundation, and placed under
86 the <a href="COPYING.DOC">GNU Free Documentation License version 1.1</a>.
87 There are no Front-Cover Texts, no Back-Cover Texts, and
88 <!-- as far as I know -->
89 no Invariant Sections.
90 </p>
92 <p>If you plan on making copies of the documentation, please let us know.
93 We can probably offer suggestions.
94 </p>
97 <!-- ####################################################### -->
99 <hr />
100 <p class="fineprint"><em>
101 Comments and suggestions about this page are welcome, and may be sent to
102 <a href="mailto:libstdc++@gcc.gnu.org">the libstdc++ mailing list</a>.
103 Comments or questions about the licenses themselves are also welcome, and
104 should be directed to the GCC list as descibed above.
105 </em></p>
108 </body>
109 </html>