1 Most of the packages that were used by Buildroot to produce the image files,
2 including Buildroot itself, have open-source licenses. It is your
3 responsibility to comply to the requirements of these licenses.
4 To make this easier for you, Buildroot collected in this directory some
5 material you may need to get it done.
7 This material is composed of the following items.
8 * The scripts used to control compilation of the packages and the generation
9 of image files, i.e. the Buildroot sources.
10 Note: this has not been saved due to technical limitations, you must
12 * The Buildroot configuration file; this has been saved in buildroot.config.
13 * The toolchain (cross-compiler and related tools) used to generate all the
15 Note: this may have not been saved due to technical limitations, you may
16 need to collect it manually.
17 * The original source code for all packages; this has been saved in the
18 sources/ subdirectory (except for the non-redistributable packages, which
19 have not been saved). Patches that were applied are also saved, along
20 with a file named 'series' that lists the patches in the order they were
21 applied. Patches are under the same license as the files that they modify
22 in the original package.
23 Note: Buildroot applies additional patches to Libtool scripts of
24 autotools-based packages. These patches can be found under
25 support/libtool in the Buildroot source and, due to technical
26 limitations, are not saved with the package sources. You may need
27 to collect them manually.
28 * A manifest file listing the configured packages and related information.
29 * The license text of the packages; they have been saved in the licenses/