| Software Name | The name of the application or files |
| Version | Version of the application or files |
| License Type | Type of license(s) under which TI will be providing software to the licensee (e.g. BSD, GPLv2, TI TSPA License, TI Commercial License). See Open Source Reference License Disclaimer in the Disclaimers Section. |
| Location | The directory name and path on the media (or in an archive) where the Package is located. |
| Delivered As | This field will either be “Source”, “Binary” or “Source and Binary“ and is the form the content of the Package is delivered in. If the Package is delivered in an archive format, this field applies to the contents of the archive. If the word Limited is used with Source, as in “Limited Source” or “Limited Source and Binary” then only portions of the Source for the application are provided. |
| Modified by TI | This field will either be “Yes” or “No”. A “Yes” means TI had made changes to the Software. A “No” means TI has not made any changes. NOTE: This field is not applicable for Software “Obtained from” TI. |
| Obtained from | This field specifies from where or from whom TI obtained the Software. It may be a URL to an Open Source site, a 3rd party companylicensor, or TI (if TI developed the software). If this field contains a link to an Open Source software, the date it was downloaded is also recorded. See Links Disclaimer in the Disclaimers Section. |
Any use of ECCNs listed in the Manifest is at the user's risk and without recourse to TI. Your company, as the exporter of record, is responsible for determining the correct classification of any item at the time of export. Any export classification by TI of Software is for TI's internal use only and shall not be construed as a representation or warranty regarding the proper export classification for such Software or whether an export license or other documentation is required for exporting such Software.
Any links appearing on this Manifest (for example in the “Obtained from” field) were verified at the time the Manifest was created. TI makes no guarantee that any listed links will remain active in the future.
Your company is responsible for confirming the applicable license terms for any open source Software listed in this Manifest that was not “Obtained from” TI. Any open source license specified in this Manifest for Sotware that was not “Obtained from” TI is for TI's internal use only and shall not be construed as a representation of warranty regarding the proper open source license terms for such Software.
ECCN for Software included in this release: Publicly Available
ECCN for Technology (e.g., user documentation, specifications) included in this release: Publicly Available
See Legend above for a description of the columns and possible values.
This table describes any GPLv3 software being delivered that is expected to run on a Development Host, instead of the target device.
Any Qt package referenced in this manifest that has LGPL 2.1 or LGPL 3 as a licensing option is only being used and distributed by TI under LGPL 2.1. The choice of having both, as reflected in the manifest table, comes from the licensing line the corresponding recipe. TI has opted to only use LGPL 2.1.
This table describes any software being delivered that is expected to run on a Development Host, instead of the target device. Some of this software may be licensed under GPLv3 but it is not expected to be shipped as a product.
Any Qt package referenced in this manifest that has LGPL 2.1 or LGPL 3 as a licensing option is only being used and distributed by TI under LGPL 2.1. The choice of having both, as reflected in the manifest table, comes from the licensing line the corresponding recipe. TI has opted to only use LGPL 2.1.
This table describes any GPLv3 software being delivered that is expected to run on the target device.
Any Qt package referenced in this manifest that has LGPL 2.1 or LGPL 3 as a licensing option is only being used and distributed by TI under LGPL 2.1. The choice of having both, as reflected in the manifest table, comes from the licensing line the corresponding recipe. TI has opted to only use LGPL 2.1.
This table describes any software being delivered that is expected to run on the target device.
Any Qt package referenced in this manifest that has LGPL 2.1 or LGPL 3 as a licensing option is only being used and distributed by TI under LGPL 2.1. The choice of having both, as reflected in the manifest table, comes from the licensing line the corresponding recipe. TI has opted to only use LGPL 2.1.
This table describes software that is installed on the development host but is not part of the linux-devkit package. This is usually software example sources or tools such a flash utilities.
Any Qt package referenced in this manifest that has LGPL 2.1 or LGPL 3 as a licensing option is only being used and distributed by TI under LGPL 2.1. The choice of having both, as reflected in the manifest table, comes from the licensing line the corresponding recipe. TI has opted to only use LGPL 2.1.
This table describes GPLv3 software libraries and headers that are installed on the development host and used during the development of software to run on the target. Customers should be careful when linking against these libraries to make sure they are complying with the license(s) of the library
Any Qt package referenced in this manifest that has LGPL 2.1 or LGPL 3 as a licensing option is only being used and distributed by TI under LGPL 2.1. The choice of having both, as reflected in the manifest table, comes from the licensing line the corresponding recipe. TI has opted to only use LGPL 2.1.
This table describes software libraries and headers that are installed on the development host and used during the development of software to run on the target. Some of this software may be licensed under GPLv3. Customers should be careful when linking against these libraries to make sure they are complying with the license(s) of the library
Any Qt package referenced in this manifest that has LGPL 2.1 or LGPL 3 as a licensing option is only being used and distributed by TI under LGPL 2.1. The choice of having both, as reflected in the manifest table, comes from the licensing line the corresponding recipe. TI has opted to only use LGPL 2.1.
Licenses can be found in the "docs/licenses" directory of the SDK install directory
Version 3.1, 31 March 2009
Copyright © 2009 Free Software Foundation, Inc. http://fsf.org/
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
This GCC Runtime Library Exception (Exception) is an additional permission under section 7 of the GNU General Public License, version 3 (GPLv3). It applies to a given file (the Runtime Library) that bears a notice placed by the copyright holder of the file stating that the file is governed by GPLv3 along with this Exception.
When you use GCC to compile a program, GCC may combine portions of certain GCC header files and runtime libraries with the compiled program. The purpose of this Exception is to allow compilation of non-GPL (including proprietary) programs to use, in this way, the header files and runtime libraries covered by this Exception.
A file is an Independent Module if it either requires the Runtime Library for execution after a Compilation Process, or makes use of an interface provided by the Runtime Library, but is not otherwise based on the Runtime Library.
GCC means a version of the GNU Compiler Collection, with or without modifications, governed by version 3 (or a specified later version) of the GNU General Public License (GPL) with the option of using any subsequent versions published by the FSF.
GPL-compatible Software is software whose conditions of propagation, modification and use would permit combination with GCC in accord with the license of GCC.
GPL-compatible Software is software whose conditions of propagation, modification and use would permit combination with GCC in accord with the license of GCC.
The Compilation Process transforms code entirely represented in non-intermediate languages designed for human-written code, and/or in Java Virtual Machine byte code, into Target Code. Thus, for example, use of source code generators and preprocessors need not be considered part of the Compilation Process, since the Compilation Process can be understood as starting with the output of the generators or preprocessors.
A Compilation Process is Eligible if it is done using GCC, alone or with other GPL-compatible software, or if it is done without using any work based on GCC. For example, using non-GPL-compatible Software to optimize any GCC intermediate representations would not qualify as an Eligible Compilation Process.
You have permission to propagate a work of Target Code formed by combining the Runtime Library with Independent Modules, even if such propagation would otherwise violate the terms of GPLv3, provided that all Target Code was generated by Eligible Compilation Processes. You may then convey such a combination under terms of your choice, consistent with the licensing of the Independent Modules.
The availability of this Exception does not imply any general presumption that third-party software is unaffected by the copyleft requirements of the license of GCC.