forked from OSchip/llvm-project
clarify that the advantages of the BSD license apply to when you incorporate clang into proprietary code bases,
patch by Jonathan Sauer. llvm-svn: 161475
This commit is contained in:
parent
ecffd83c85
commit
b35f34105e
|
@ -329,13 +329,15 @@ specifically designed and built to capture this information.
|
|||
<!--=======================================================================-->
|
||||
|
||||
<p>We actively intend for clang (and LLVM as a whole) to be used for
|
||||
commercial projects, and the BSD license is the simplest way to allow this. We
|
||||
feel that the license encourages contributors to pick up the source and work
|
||||
with it, and believe that those individuals and organizations will contribute
|
||||
back their work if they do not want to have to maintain a fork forever (which is
|
||||
time consuming and expensive when merges are involved). Further, nobody makes
|
||||
money on compilers these days, but many people need them to get bigger goals
|
||||
accomplished: it makes sense for everyone to work together.</p>
|
||||
commercial projects, not only as a stand-alone compiler but also as a library
|
||||
embedded inside a proprietary application. The BSD license is the simplest way
|
||||
to allow this. We feel that the license encourages contributors to pick up the
|
||||
source and work with it, and believe that those individuals and organizations
|
||||
will contribute back their work if they do not want to have to maintain a fork
|
||||
forever (which is time consuming and expensive when merges are involved).
|
||||
Further, nobody makes money on compilers these days, but many people need them
|
||||
to get bigger goals accomplished: it makes sense for everyone to work
|
||||
together.</p>
|
||||
|
||||
<p>For more information about the LLVM/clang license, please see the <a
|
||||
href="http://llvm.org/docs/DeveloperPolicy.html#license">LLVM License
|
||||
|
|
Loading…
Reference in New Issue