On 1/21/2010 1:09 PM, Hanno Schlichting wrote: > - Who holds the copyright, is there a foundation or is there a risk of > the project getting into trouble because of copyright issues? > - What licence is the code and the tools under and what affect does > that have on the code generated by the JIT compiler?
http://llvm.org/docs/DeveloperPolicy.html#clp """ We intend to keep LLVM perpetually open source and to use a liberal open source license. The current license is the University of llinois/NCSA Open Source License[1], which boils down to this: * You can freely distribute LLVM. * You must retain the copyright notice if you redistribute LLVM. * Binaries derived from LLVM must reproduce the copyright notice (e.g. in an included readme file). * You can't use our names to promote your LLVM derived products. * There's no warranty on LLVM at all. We believe this fosters the widest adoption of LLVM because it allows commercial products to be derived from LLVM with few restrictions and without a requirement for making any derived works also open source (i.e. LLVM's license is not a "copyleft" license like the GPL). We suggest that you read the License[1] if further clarification is needed. """ """ We have no plans to change the license of LLVM. If you have questions or comments about the license, please contact the LLVM Oversight Group[2]. """ [1] http://www.opensource.org/licenses/UoI-NCSA.php [2] llvm-oversi...@cs.uiuc.edu -- Scott Dial sc...@scottdial.com scod...@cs.indiana.edu _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
