From 9a58584bb13d725ecb1ac70ce91c6ac52daa9484 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Wed, 8 Aug 2012 05:26:51 +0000 Subject: [PATCH] clarify that the advantages of the BSD license apply to when you incorporate clang into proprietary code bases, patch by Jonathan Sauer. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@161475 91177308-0d34-0410-b5e6-96231b3b80d8 --- www/features.html | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/www/features.html b/www/features.html index d55391a34f..2d3191e685 100644 --- a/www/features.html +++ b/www/features.html @@ -329,13 +329,15 @@ specifically designed and built to capture this information.

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.

+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.

For more information about the LLVM/clang license, please see the LLVM License -- 2.40.0