d-two/operating-system
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Migrate Buildroot 2019.02.9 (#539)

Browse Source
This commit is contained in:
Pascal Vizeli
2020-01-13 14:47:52 +01:00
committed by GitHub
parent d6a700565e
commit 13e4578b7a
139 changed files with 898 additions and 1178 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
buildroot/docs/manual/adding-packages-generic.txt
View File

@@ -358,9 +358,11 @@ not and can not work as people would expect it should:
* +LIBFOO_DEPENDENCIES+ lists the dependencies (in terms of package
name) that are required for the current target package to
compile. These dependencies are guaranteed to be compiled and
installed before the configuration of the current package starts. In
a similar way, +HOST_LIBFOO_DEPENDENCIES+ lists the dependencies for
the current host package.
installed before the configuration of the current package starts.
However, modifications to configuration of these dependencies will
not force a rebuild of the current package. In a similar way,
+HOST_LIBFOO_DEPENDENCIES+ lists the dependencies for the current
host package.
* +LIBFOO_EXTRACT_DEPENDENCIES+ lists the dependencies (in terms of
package name) that are required for the current target package to be

38
buildroot/docs/manual/manual.html
View File

File diff suppressed because one or more lines are too long

BIN
buildroot/docs/manual/manual.pdf
View File

Binary file not shown.

21
buildroot/docs/manual/manual.text
View File

@@ -161,13 +161,13 @@ List of Examples
---------------------------------------------------------------------
Buildroot 2019.02.8 manual generated on 2019-12-07 19:24:23 UTC from
git revision aaa1437b11
Buildroot 2019.02.9 manual generated on 2020-01-12 15:28:51 UTC from
git revision 24f25c8d23
The Buildroot manual is written by the Buildroot developers. It is
licensed under the GNU General Public License, version 2. Refer to
the COPYING [http://git.buildroot.org/buildroot/tree/COPYING?id=
aaa1437b110f886ee24757595542f715a77d702a] file in the Buildroot
24f25c8d23bd85d57b6e9c776f2c7716f2ddd4af] file in the Buildroot
sources for the full text of this license.
Copyright © 2004-2019 The Buildroot developers
@@ -1197,6 +1197,15 @@ can help you understand how to work with Buildroot:
overlay, a post-build script or a post-image script are made,
there is no need for a full rebuild: a simple make invocation
will take the changes into account.
* When a package listed in FOO_DEPENDENCIES is rebuilt or removed,
the package foo is not automatically rebuilt. For example, if a
package bar is listed in FOO_DEPENDENCIES with FOO_DEPENDENCIES =
bar and the configuration of the bar package is changed, the
configuration change would not result in a rebuild of package foo
automatically. In this scenario, you may need to either rebuild
any packages in your build which reference bar in their
DEPENDENCIES, or perform a full rebuild to ensure any bar
dependent packages are up to date.
Generally speaking, when you’re facing a build error and you’re
unsure of the potential consequences of the configuration changes
@@ -4369,8 +4378,10 @@ information is (assuming the package name is libfoo) :
name) that are required for the current target package to
compile. These dependencies are guaranteed to be compiled and
installed before the configuration of the current package starts.
In a similar way, HOST_LIBFOO_DEPENDENCIES lists the dependencies
for the current host package.
However, modifications to configuration of these dependencies
will not force a rebuild of the current package. In a similar
way, HOST_LIBFOO_DEPENDENCIES lists the dependencies for the
current host package.
* LIBFOO_EXTRACT_DEPENDENCIES lists the dependencies (in terms of
package name) that are required for the current target package to
be extracted. These dependencies are guaranteed to be compiled

10
buildroot/docs/manual/rebuilding-packages.txt
View File

@@ -65,6 +65,16 @@ can help you understand how to work with Buildroot:
there is no need for a full rebuild: a simple +make+ invocation
will take the changes into account.
* When a package listed in +FOO_DEPENDENCIES+ is rebuilt or removed,
the package +foo+ is not automatically rebuilt. For example, if a
package +bar+ is listed in +FOO_DEPENDENCIES+ with +FOO_DEPENDENCIES
= bar+ and the configuration of the +bar+ package is changed, the
configuration change would not result in a rebuild of package +foo+
automatically. In this scenario, you may need to either rebuild any
packages in your build which reference +bar+ in their +DEPENDENCIES+,
or perform a full rebuild to ensure any +bar+ dependent packages are
up to date.
Generally speaking, when you're facing a build error and you're unsure
of the potential consequences of the configuration changes you've
made, do a full rebuild. If you get the same build error, then you are