docs/manual/legal-notice.txt

1 // -*- mode:doc; -*-
4 [[legal-info]]
16 Some licenses require you to publish the license text in the documentation of
27 --------------------
28 make legal-info
29 --------------------
31 Buildroot will collect legally-relevant material in your output directory,
32 under the +legal-info/+ subdirectory.
41   +host-sources/+ subdirectories for target and host packages respectively.
48   autotools-based packages. These patches can be found under
49   +support/libtool+ in the Buildroot source and, due to technical
56 * The license texts of all packages, in the +licenses/+ and +host-licenses/+
61 Please note that the aim of the +legal-info+ feature of Buildroot is to
66 for packages released under BSD-like licenses, that you are not required to
69 Moreover, due to technical limitations, Buildroot does not produce some
72 When you run +make legal-info+, Buildroot produces warnings in the +README+
75 Finally, keep in mind that the output of +make legal-info+ is based on
81 of +make legal-info+ before using it as your own compliance delivery. See
85 [[legal-info-buildroot]]
89 http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU General
99 when releasing a product that contains GPL-licensed software.
101 http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU GPL]
122 See xref:patch-policy[] for the technical details.