2 // vim: set syntax=asciidoc:
6 == Legal notice and licensing
8 === Complying with open source licenses
10 All of the end products of Buildroot (toolchain, root filesystem, kernel,
11 bootloaders) contain open source software, released under various licenses.
13 Using open source software gives you the freedom to build rich embedded
14 systems, choosing from a wide range of packages, but also imposes some
15 obligations that you must know and honour.
16 Some licenses require you to publish the license text in the documentation of
17 your product. Others require you to redistribute the source code of the
18 software to those that receive your product.
20 The exact requirements of each license are documented in each package, and
21 it is your responsibility (or that of your legal office) to comply with those
23 To make this easier for you, Buildroot can collect for you some material you
24 will probably need. To produce this material, after you have configured
25 Buildroot with +make menuconfig+, +make xconfig+ or +make gconfig+, run:
31 Buildroot will collect legally-relevant material in your output directory,
32 under the +legal-info/+ subdirectory.
35 * A +README+ file, that summarizes the produced material and contains warnings
36 about material that Buildroot could not produce.
37 * +buildroot.config+: this is the Buildroot configuration file that is usually
38 produced with +make menuconfig+, and which is necessary to reproduce the
40 * The source code for all packages; this is saved in the +sources/+ and
41 +host-sources/+ subdirectories for target and host packages respectively.
42 The source code for packages that set +<PKG>_REDISTRIBUTE = NO+ will not be
44 Patches applied to some packages by Buildroot are distributed with the
45 Buildroot sources and are not duplicated in the +sources/+ and +host-sources/+
47 * A manifest file (one for host and one for target packages) listing the
48 configured packages, their version, license and related information.
49 Some of this information might not be defined in Buildroot; such items are
51 * The license texts of all packages, in the +licenses/+ and +host-licenses/+
52 subdirectories for target and host packages respectively.
53 If the license file(s) are not defined in Buildroot, the file is not produced
54 and a warning in the +README+ indicates this.
56 Please note that the aim of the +legal-info+ feature of Buildroot is to
57 produce all the material that is somehow relevant for legal compliance with the
58 package licenses. Buildroot does not try to produce the exact material that
59 you must somehow make public. Certainly, more material is produced than is
60 needed for a strict legal compliance. For example, it produces the source code
61 for packages released under BSD-like licenses, that you are not required to
62 redistribute in source form.
64 Moreover, due to technical limitations, Buildroot does not produce some
65 material that you will or may need, such as the toolchain source code and the
66 Buildroot source code itself (including patches to packages for which source
67 distribution is required).
68 When you run +make legal-info+, Buildroot produces warnings in the +README+
69 file to inform you of relevant material that could not be saved.
71 [[legal-info-list-licenses]]
72 === License abbreviations
74 Here is a list of the licenses that are most widely used by packages in
75 Buildroot, with the name used in the manifest files:
78 http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[
79 GNU General Public License, version 2];
81 http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[
82 GNU General Public License, version 2]
83 or (at your option) any later version;
85 http://www.gnu.org/licenses/gpl.html[
86 GNU General Public License, version 3];
88 http://www.gnu.org/licenses/gpl.html[
89 GNU General Public License, version 3]
90 or (at your option) any later version;
92 http://www.gnu.org/licenses/gpl.html[
93 GNU General Public License] (any version);
95 http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html[
96 GNU Library General Public License, version 2];
98 http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html[
99 GNU Library General Public License, version 2]
100 or (at your option) any later version;
102 http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html[
103 GNU Lesser General Public License, version 2.1];
105 http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html[
106 GNU Lesser General Public License, version 2.1]
107 or (at your option) any later version;
109 http://www.gnu.org/licenses/lgpl.html[
110 GNU Lesser General Public License, version 3];
112 http://www.gnu.org/licenses/lgpl.html[
113 GNU Lesser General Public License, version 3]
114 or (at your option) any later version;
116 http://www.gnu.org/licenses/lgpl.html[
117 GNU Lesser General Public License] (any version);
119 http://directory.fsf.org/wiki/License:BSD_4Clause[
120 Original BSD 4-clause license];
122 http://opensource.org/licenses/BSD-3-Clause[
123 BSD 3-clause license];
125 http://opensource.org/licenses/BSD-2-Clause[
126 BSD 2-clause license];
128 http://opensource.org/licenses/mit-license.html[
131 http://apache.org/licenses/LICENSE-2.0.html[
132 Apache License, version 2.0];
134 === Complying with the Buildroot license
136 Buildroot itself is an open source software, released under the
137 http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU General Public
138 License, version 2] or (at your option) any later version.
139 However, being a build system, it is not normally part of the end product:
140 if you develop the root filesystem, kernel, bootloader or toolchain for a
141 device, the code of Buildroot is only present on the development machine, not
142 in the device storage.
144 Nevertheless, the general view of the Buildroot developers is that you should
145 release the Buildroot source code along with the source code of other packages
146 when releasing a product that contains GPL-licensed software.
148 http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU GPL]
149 defines the "'complete source code'" for an executable work as "'all the
150 source code for all modules it contains, plus any associated interface
151 definition files, plus the scripts used to control compilation and installation
153 Buildroot is part of the 'scripts used to control compilation and
154 installation of the executable', and as such it is considered part of the
155 material that must be redistributed.
157 Keep in mind that this is only the Buildroot developers' opinion, and you
158 should consult your legal department or lawyer in case of any doubt.