diff options
Diffstat (limited to 'docs/manual')
| -rw-r--r-- | docs/manual/legal-notice.txt | 11 | ||||
| -rw-r--r-- | docs/manual/patch-policy.txt | 8 | ||||
| -rw-r--r-- | docs/manual/using-buildroot-development.txt | 2 |
3 files changed, 13 insertions, 8 deletions
diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt index 0572daee34..7c19bc30ab 100644 --- a/docs/manual/legal-notice.txt +++ b/docs/manual/legal-notice.txt @@ -41,9 +41,14 @@ There you will find: +host-sources/+ subdirectories for target and host packages respectively. The source code for packages that set +<PKG>_REDISTRIBUTE = NO+ will not be saved. - Patches applied to some packages by Buildroot are distributed with the - Buildroot sources and are not duplicated in the +sources/+ and +host-sources/+ - subdirectories. + Patches that were applied are also saved, along with a file named +series+ + that lists the patches in the order they were applied. Patches are under the + same license as the files that they modify. + Note: Buildroot applies additional patches to Libtool scripts of + autotools-based packages. These patches can be found under + +support/libtool+ in the Buildroot source and, due to technical + limitations, are not saved with the package sources. You may need to + collect them manually. * A manifest file (one for host and one for target packages) listing the configured packages, their version, license and related information. Some of this information might not be defined in Buildroot; such items are diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt index 5a1fe4f46e..e1df8b003f 100644 --- a/docs/manual/patch-policy.txt +++ b/docs/manual/patch-policy.txt @@ -73,12 +73,12 @@ details. * If a +series+ file exists in the package directory, then patches are applied according to the +series+ file; + -* Otherwise, patch files matching +<packagename>-*.patch+ - are applied in alphabetical order. +* Otherwise, patch files matching +*.patch+ are applied in alphabetical + order. So, to ensure they are applied in the right order, it is highly recommended to name the patch files like this: - +<packagename>-<number>-<description>.patch+, where +<number>+ - refers to the 'apply order'. + +<number>-<description>.patch+, where +<number>+ refers to the + 'apply order'. . If +BR2_GLOBAL_PATCH_DIR+ is defined, the directories will be enumerated in the order they are specified. The patches are applied diff --git a/docs/manual/using-buildroot-development.txt b/docs/manual/using-buildroot-development.txt index a075416ba1..e167849cdc 100644 --- a/docs/manual/using-buildroot-development.txt +++ b/docs/manual/using-buildroot-development.txt @@ -8,7 +8,7 @@ it, configure, compile and install the software component found inside this tarball. The source code is extracted in +output/build/<package>-<version>+, which is a temporary directory: whenever +make clean+ is used, this directory is entirely removed, and -re-recreated at the next +make+ invocation. Even when a Git or +re-created at the next +make+ invocation. Even when a Git or Subversion repository is used as the input for the package source code, Buildroot creates a tarball out of it, and then behaves as it normally does with tarballs. |
