Add a section on licensing questions.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9504 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Vikram S. Adve 2003-10-25 17:06:55 +00:00
parent 764486f5e4
commit 04da65a454

View File

@ -8,6 +8,45 @@ LLVM: Frequently Asked Questions
<hr>
<!--=====================================================================-->
<h2>
<a name="license">Licenses</a>
</h2>
<!--=====================================================================-->
<dl compact>
<dt> <b>Why are the LLVM source code and the front-end distributed
under different licenses?</b>
<dd>
The C/C++ front-ends are based on GCC and must be distributed under
the GPL. Our aim is to distribute LLVM source code are a <em>much
less restrictive</em> license, in particular one that does not
compel users who distribute tools based on modifying the source to
redistribute the modified source code as well.
<dt><b>Does the Illinois Open Source License really qualify
as an "open source" license?</b>
<dd>The
<a href="http://www.opensource.org/licenses/UoI-NCSA.php">
UI Open Source License</a> is certified by the
Open Source Initiative (OSI).
<dt> <b>Can I modify LLVM source code and redistribute the modified
source?</b>
<dd>
Yes. The modified source distribution must retain notice both the
copyright notice and follow the three bulletted conditions listed in
the <a href="releases/1.0/LICENSE.txt">LLVM license</a>.
<dt> <b>Can I modify LLVM source code and redistribute binaries or
other tools based on it, without redistributing the source.
<dd>
Yes, this is why we distribute LLVM under a less restrictive license
than GPL, as explained in the first question above.
<p>
</dl>
<hr>
<!--=====================================================================-->
<h2>
<a name="source">Source Code</a>