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

Update buildroot to 2021.02.1 (#1312)

Browse Source 
Signed-off-by: Stefan Agner <stefan@agner.ch>
This commit is contained in:
Stefan Agner
2021-04-08 15:51:24 +02:00
committed by GitHub
parent 40a705bbd3
commit aff28ce60e
411 changed files with 28197 additions and 879 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
buildroot/docs/manual/adding-packages-tips.txt
View File

@@ -174,8 +174,8 @@ past, the 'github' helper function should be used as shown below.
------------------------
# Use a tag or a full commit ID
FOO_VERSION = v1.0
FOO_SITE = $(call github,<user>,<package>,$(FOO_VERSION))
FOO_VERSION = 1.0
FOO_SITE = $(call github,<user>,<package>,v$(FOO_VERSION))
------------------------
.Notes
@@ -184,6 +184,12 @@ FOO_SITE = $(call github,<user>,<package>,$(FOO_VERSION))
Buildroot (e.g.: +foo-f6fb6654af62045239caed5950bc6c7971965e60.tar.gz+),
so it is not necessary to specify it in the +.mk+ file.
- When using a commit ID as version, you should use the full 40 hex characters.
- When the tag contains a prefix such as +v+ in +v1.0+, then the
+VERSION+ variable should contain just +1.0+, and the +v+ should be
added directly in the +SITE+ variable, as illustrated above. This
ensures that the +VERSION+ variable value can be used to match
against http://www.release-monitoring.org/[release-monitoring.org]
results.
If the package you wish to add does have a release section on GitHub, the
maintainer may have uploaded a release tarball, or the release may just point
@@ -204,3 +210,33 @@ image::github_hash_mongrel2.png[]
- On the other hand, if there's is *only* the "Source code" link, then
it's an automatically generated tarball and you should use the
'github' helper function.
[[gitlab-download-url]]
==== How to add a package from Gitlab
In a similar way to the +github+ macro described in
xref:github-download-url[], Buildroot also provides the +gitlab+ macro
to download from Gitlab repositories. It can be used to download
auto-generated tarballs produced by Gitlab, either for specific tags
or commits:
------------------------
# Use a tag or a full commit ID
FOO_VERSION = 1.0
FOO_SITE = $(call gitlab,<user>,<package>,v$(FOO_VERSION))
------------------------
By default, it will use a +.tar.gz+ tarball, but Gitlab also provides
+.tar.bz2+ tarballs, so by adding a +<pkg>_SOURCE+ variable, this
+.tar.bz2+ tarball can be used:
------------------------
# Use a tag or a full commit ID
FOO_VERSION = 1.0
FOO_SITE = $(call gitlab,<user>,<package>,v$(FOO_VERSION))
FOO_SOURCE = foo-$(FOO_VERSION).tar.bz2
------------------------
If there is a specific tarball uploaded by the upstream developers in
+https://gitlab.com/<project>/releases/+, do not use this macro, but
rather use directly the link to the tarball.

36
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.

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

@@ -174,13 +174,13 @@ List of Examples
---------------------------------------------------------------------
Buildroot 2021.02 manual generated on 2021-03-06 21:24:27 UTC from
git revision e2fba6457b
Buildroot 2021.02.1 manual generated on 2021-04-07 10:22:25 UTC from
git revision 6668381363
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=
e2fba6457bd9d9c720540332eaf0c1f8c29eab00] file in the Buildroot
6668381363364c89d43689322cc5ce4249c8fd9d] file in the Buildroot
sources for the full text of this license.
Copyright © 2004-2020 The Buildroot developers
@@ -7186,8 +7186,8 @@ mechanisms in the past, the github helper function should be used as
shown below.
# Use a tag or a full commit ID
FOO_VERSION = v1.0
FOO_SITE = $(call github,<user>,<package>,$(FOO_VERSION))
FOO_VERSION = 1.0
FOO_SITE = $(call github,<user>,<package>,v$(FOO_VERSION))
Notes
@@ -7198,6 +7198,12 @@ Notes
not necessary to specify it in the .mk file.
* When using a commit ID as version, you should use the full 40 hex
characters.
* When the tag contains a prefix such as v in v1.0, then the
VERSION variable should contain just 1.0, and the v should be
added directly in the SITE variable, as illustrated above. This
ensures that the VERSION variable value can be used to match
against release-monitoring.org [http://www.release-monitoring.org
/] results.
If the package you wish to add does have a release section on GitHub,
the maintainer may have uploaded a release tarball, or the release
@@ -7217,6 +7223,31 @@ tag:
then it’s an automatically generated tarball and you should use
the github helper function.
18.24.5. How to add a package from Gitlab
In a similar way to the github macro described in Section 18.24.4,
“How to add a package from GitHub”, Buildroot also provides the
gitlab macro to download from Gitlab repositories. It can be used to
download auto-generated tarballs produced by Gitlab, either for
specific tags or commits:
# Use a tag or a full commit ID
FOO_VERSION = 1.0
FOO_SITE = $(call gitlab,<user>,<package>,v$(FOO_VERSION))
By default, it will use a .tar.gz tarball, but Gitlab also provides
.tar.bz2 tarballs, so by adding a <pkg>_SOURCE variable, this
.tar.bz2 tarball can be used:
# Use a tag or a full commit ID
FOO_VERSION = 1.0
FOO_SITE = $(call gitlab,<user>,<package>,v$(FOO_VERSION))
FOO_SOURCE = foo-$(FOO_VERSION).tar.bz2
If there is a specific tarball uploaded by the upstream developers in
https://gitlab.com/<project>/releases/, do not use this macro, but
rather use directly the link to the tarball.
18.25. Conclusion
As you can see, adding a software package to Buildroot is simply a