mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-02-20 08:29:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

bitbake: doc: bitbake-user-manual: ref-variables: order alphabetically the glossary sources

Browse Source 
This reorders a few entry so that they are alphabetically sorted.

(Bitbake rev: 311350ed5cb164d975c2119e60255a409e27dffb)

Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Signed-off-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Quentin Schulz
2021-07-26 17:35:22 +02:00
committed by Richard Purdie
parent bf58b597d2
commit eb38dce0c1
1 changed files with 27 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
View File

@@ -231,23 +231,23 @@ overview of their function and contents.
based on the interval occur each time a respective interval is
reached beyond the initial warning (i.e. 1 Gbytes and 100 Kbytes).
:term:`BB_ENV_WHITELIST`
Specifies the internal whitelist of variables to allow through from
the external environment into BitBake's datastore. If the value of
this variable is not specified (which is the default), the following
list is used: :term:`BBPATH`, :term:`BB_PRESERVE_ENV`,
:term:`BB_ENV_WHITELIST`, and :term:`BB_ENV_EXTRAWHITE`.
:term:`BB_ENV_EXTRAWHITE`
Specifies an additional set of variables to allow through (whitelist)
from the external environment into BitBake's datastore. This list of
variables are on top of the internal list set in
:term:`BB_ENV_WHITELIST`.
.. note::
You must set this variable in the external environment in order
for it to work.
:term:`BB_ENV_EXTRAWHITE`
Specifies an additional set of variables to allow through (whitelist)
from the external environment into BitBake's datastore. This list of
variables are on top of the internal list set in
:term:`BB_ENV_WHITELIST`.
:term:`BB_ENV_WHITELIST`
Specifies the internal whitelist of variables to allow through from
the external environment into BitBake's datastore. If the value of
this variable is not specified (which is the default), the following
list is used: :term:`BBPATH`, :term:`BB_PRESERVE_ENV`,
:term:`BB_ENV_WHITELIST`, and :term:`BB_ENV_EXTRAWHITE`.
.. note::
@@ -276,18 +276,6 @@ overview of their function and contents.
BB_GENERATE_MIRROR_TARBALLS = "1"
:term:`BB_HASHCONFIG_WHITELIST`
Lists variables that are excluded from base configuration checksum,
which is used to determine if the cache can be reused.
One of the ways BitBake determines whether to re-parse the main
metadata is through checksums of the variables in the datastore of
the base configuration data. There are variables that you typically
want to exclude when checking whether or not to re-parse and thus
rebuild the cache. As an example, you would usually exclude ``TIME``
and ``DATE`` because these variables are always changing. If you did
not exclude them, BitBake would never reuse the cache.
:term:`BB_HASHBASE_WHITELIST`
Lists variables that are excluded from checksum and dependency data.
Variables that are excluded can therefore change without affecting
@@ -309,6 +297,18 @@ overview of their function and contents.
However, the more accurate the data returned, the more efficient the
build will be.
:term:`BB_HASHCONFIG_WHITELIST`
Lists variables that are excluded from base configuration checksum,
which is used to determine if the cache can be reused.
One of the ways BitBake determines whether to re-parse the main
metadata is through checksums of the variables in the datastore of
the base configuration data. There are variables that you typically
want to exclude when checking whether or not to re-parse and thus
rebuild the cache. As an example, you would usually exclude ``TIME``
and ``DATE`` because these variables are always changing. If you did
not exclude them, BitBake would never reuse the cache.
:term:`BB_HASHSERVE`
Specifies the Hash Equivalence server to use.
@@ -357,15 +357,15 @@ overview of their function and contents.
running builds when not connected to the Internet, and when operating
in certain kinds of firewall environments.
:term:`BB_NUMBER_PARSE_THREADS`
Sets the number of threads BitBake uses when parsing. By default, the
number of threads is equal to the number of cores on the system.
:term:`BB_NUMBER_THREADS`
The maximum number of tasks BitBake should run in parallel at any one
time. If your host development system supports multiple cores, a good
rule of thumb is to set this variable to twice the number of cores.
:term:`BB_NUMBER_PARSE_THREADS`
Sets the number of threads BitBake uses when parsing. By default, the
number of threads is equal to the number of cores on the system.
:term:`BB_ORIGENV`
Contains a copy of the original external environment in which BitBake
was run. The copy is taken before any whitelisted variable values are