CAREFULLY READ THIS COLLECTION OF INFORMATION AND LICENSE AGREEMENTS. BY CLICKING THE "ACCEPT" OR "AGREE" BUTTON, OR OTHERWISE ACCESSING, DOWNLOADING, INSTALLING OR USING THE SOFTWARE, YOU AGREE ON BEHALF OF LICENSEE TO BE BOUND BY THIS INFORMATION AND LICENSE AGREEMENTS (TO THE EXTENT APPLICABLE TO THE SPECIFIC SOFTWARE YOU OBTAIN AND THE SPECIFIC MANNER IN WHICH YOU USE SUCH SOFTWARE). IF LICENSEE DOES NOT AGREE TO ALL OF THE INFORMATION AND LICENSE AGREEMENTS BELOW, DO NOT CLICK THE "ACCEPT" OR "AGREE" BUTTON OR ACCESS, DOWNLOAD, INSTALL OR USE THE SOFTWARE; AND IF LICENSEE HAS ALREADY OBTAINED THE SOFTWARE FROM AN AUTHORIZED SOURCE, PROMPTLY RETURN IT FOR A REFUND. Part One: Overview. The following information applies to certain items of third-party technology that are included along with certain Xilinx software tools. The Xilinx Embedded Development Kit (EDK) is a suite of software and other technology that enables Licensee to design a complete embedded processor system for use in a Xilinx Device. EDK includes, among other components, (a) the Xilinx Platform Studio (XPS), which is the development environment, or GUI, used for designing the hardware portion of an embedded processor system; and (b) the Xilinx Software Development Kit (SDK), which is an integrated development environment, complementary to XPS, that is used to create and verify C/C++ embedded software applications. SDK is also made available separately from EDK. Licensee's use of the GNU compilers (including associated libraries and utilities) that are supplied with SDK may cause Licensee's software application (or board- support package) to be governed by certain third-party "open source" license agreements, as further described below. Licensee can avoid this result by using alternative compilers, libraries, and utilities of its own choosing in lieu of the GNU compilers (and associated libraries and utilities) supplied with SDK. First: Xilinx provides three types of software drivers: (a) stand-alone drivers, (b) VxWorks drivers, and (c) Linux drivers. The Linux drivers are made available under the terms of the GNU GPL and are subject to that license. Second: Compiling (i.e., used for C/C++ code/drivers) with the GNU compilers will add certain "newlib" utilities to Licensee's software application. The specific utility or utilities chosen by the Licensee will be covered under one or more of the various licenses set forth in the collection of "newlib" licenses described below. Third: Compiling (i.e., used for C/C++ code/drivers) with the GNU compilers adds certain "start up" code to Licensee's software application. This "start up" code may be covered under the GNU LGPL, or, alternatively, there may be other license terms (including possible exceptions or exemptions from certain obligations of the GNU licenses) governing such "start up" code which would be contained or described in the header files or other accompanying source files for such "start up" code. Fourth: If the Licensee chooses to use the LWIP stack, the LWIP code becomes part of Licensee's software application. The LWIP code is covered by a license described below. Note: Licensee is solely responsible for checking the header files and other accompanying source files of all software applications created from the use of the GNU compliers (and associated libraries and utilities) that are supplied with SDK because such header and/or source files may contain or describe various copyright notices and license terms and conditions governing such files, which vary from case to case based on Licensee's usage and are beyond the control of Xilinx. This summary and the license information provided below is for reference purposes and is not intended to be a comprehensive list of all copyright notices or third-party license terms and conditions applicable to SDK. Licensee is solely responsible for complying with the terms and conditions imposed by third parties as applicable to the Licensee's software applications created from the use of the GNU compilers (and associated libraries and utilities) that are supplied with SDK. The remainder of this document is organized into various parts, as follows: Part Two: Licensee Redistributable Content. Index: Licenses and Notices: Part Two contains a list of notices, licenses and/or other information related to certain items of third-party technology that Xilinx has identified and categorized as "Licensee Redistributable Content", which means that Xilinx has included this third- party technology with the Xilinx Software for the purpose of enabling a Xilinx customer to distribute it (or a portion of it, or a derivative form of it) as part of such customer's design or product. Part Three: Other Third-Party Content. Index: Licenses and Notices: Part Three contains a list of additional notices, licenses and/or other information related to certain items of third-party technology other than as provided in Part Two. Please note that by listing certain items in this Part Three as opposed to Part Two above, Xilinx does not abrogate or diminish in any respect either its own obligations, or Licensee's rights (if and as may be applicable), with respect to the (present or future) distribution of such items. With respect to any license that requires Xilinx to make available to recipients of object code distributed by Xilinx pursuant to such license the corresponding source code, and if you desire to receive such source code from Xilinx and cannot access the internet to obtain a copy thereof, then Xilinx hereby offers (which offer is valid for as long as required by the applicable license; and we may charge you the cost thereof unless prohibited by the license) to provide you with a copy of such source code; and to accept such offer send a letter requesting such source code (please be specific by identifying the particular Xilinx Software you are inquiring about (name and version number), to: Xilinx, Inc., Legal Department, Attention: Software Compliance Officer, 2100 Logic Drive, San Jose, CA U.S.A. 95124. Part Four: Certain Third-Party Template Licenses. Index: Text of Template Licenses: Part Five: Additional Acknowledgements. Part Two: Licensee Redistributable Content. Index: gcc (for MicroBlaze) gcc (for PowerPC) gcc (added 3/30/2012) IBM PowerPC Performance Libraries Linux Kernel and BSP files LWIP 1.3.0 LWIP 1.4.0 newlib (for MicroBlaze) newlib (for PowerPC) newlib (added 3/30/2012) Sourcery CodeBench Lite for Xilinx Cortex-A9 (both EABI and GNU/Linux) WindRiver BSP Template Files Licenses and Notices: gcc (for MicroBlaze) <<<<<<<<<<xilinx-separator>>>>>>>>>> ####################################### FILE: ./gcc/COPYING.LIB FILE: ./libiberty/COPYING.LIB FILE: ./COPYING.LIB ####################################### The text of the GNU Lesser General Public License, Version 2.1, a copy of which is made available below in Part Four of this document, was originally presented here, or as applicable, applies to the above-listed file(s). ####################################### FILE: ./gcc/COPYING FILE: ./libstdc++-v3/docs/html/17_intro/COPYING FILE: ./COPYING FILE: ./include/COPYING FILE: ./fastjar/COPYING ####################################### The text of the GNU General Public License, Version 2, a copy of which is made available below in Part Four of this document, was originally presented here, or as applicable, applies to the above-listed file(s). ####################################### FILE: ./libstdc++-v3/docs/html/17_intro/COPYING.DOC ####################################### The text of the GNU Free Documentation License, Version 1.1, a copy of which is made available below in Part Four of this document, was originally presented here, or as applicable, applies to the above-listed file. ####################################### FILE: ./libstdc++-v3/docs/html/17_intro/license.html ####################################### There are two licenses affecting GNU libstdc++-v3: one for the code, and one for the documentation. Here we will describe both of them, and try to answer some of the widespread questions. If you have more questions, ask the FSF or the gcc mailing list; the person writing this page is a programmer, not a lawyer. The Code: Runtime GPL The source code of libstdc++-v3 is distributed under version 2 of the*** GNU General Public License, with the so-called runtime exception; as follows (or see any header or implementation file): As a special exception, you may use this file as part of a free software library without restriction. Specifically, if other files instantiate templates or use macros or inline functions from this file, or you compile this file and link it with other files to produce an executable, this file does not by itself cause the resulting executable to be covered by the GNU General Public License. This exception does not however invalidate any other reasons why the executable file might be covered by the GNU General Public License. Hopefully that text is self-explanatory. If it isn't, you need to speak to your lawyer, or the Free Software Foundation. -- Most of the Q&A's are based on, paraphrased from, and outright stolen from this thread: http://gcc.gnu.org/ml/libstdc++/2000-q2/subjects.html#00050 Q: So any program which uses libstdc++ falls under the GPL? A: No. The special exception permits use of the library in proprietary applications. Q: How is that different from the GNU {Lesser,Library} GPL -- Quoting Jason Merrill from the thread above: -- A: The LGPL requires that users be able to replace the LGPL code with a modified version; this is trivial if the library in question is a C shared library. But there's no way to make that work with C++, where much of the library consists of inline functions and templates, which are expanded inside the code that uses the library. So to allow people to replace the library code, someone using the library would have to distribute their own source, rendering the LGPL equivalent to the GPL. Q: I see. So, what restrictions are there on programs that use the library? A: None.