mirror of
https://git.yoctoproject.org/poky
synced 2026-01-29 21:08:42 +01:00
bitbake: bitbake-user-manual: explicit variables taking a colon separated list
[YOCTO #15128] (Bitbake rev: d1779e2f7789e516efae434b3781c981d0ef4ded) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
18df7280ce
commit
3ba736c6cd
@@ -920,9 +920,9 @@ overview of their function and contents.
|
||||
section.
|
||||
|
||||
:term:`BBPATH`
|
||||
Used by BitBake to locate class (``.bbclass``) and configuration
|
||||
(``.conf``) files. This variable is analogous to the ``PATH``
|
||||
variable.
|
||||
A colon-separated list used by BitBake to locate class (``.bbclass``)
|
||||
and configuration (``.conf``) files. This variable is analogous to the
|
||||
``PATH`` variable.
|
||||
|
||||
If you run BitBake from a directory outside of the build directory,
|
||||
you must be sure to set :term:`BBPATH` to point to the build directory.
|
||||
@@ -1165,8 +1165,8 @@ overview of their function and contents.
|
||||
order.
|
||||
|
||||
:term:`OVERRIDES`
|
||||
BitBake uses :term:`OVERRIDES` to control what variables are overridden
|
||||
after BitBake parses recipes and configuration files.
|
||||
A colon-separated list that BitBake uses to control what variables are
|
||||
overridden after BitBake parses recipes and configuration files.
|
||||
|
||||
Following is a simple example that uses an overrides list based on
|
||||
machine architectures: OVERRIDES = "arm:x86:mips:powerpc" You can
|
||||
@@ -1225,9 +1225,9 @@ overview of their function and contents.
|
||||
PREFERRED_PROVIDER_virtual/libgl ?= "mesa"
|
||||
|
||||
:term:`PREFERRED_PROVIDERS`
|
||||
Determines which recipe should be given preference for cases where
|
||||
multiple recipes provide the same item. Functionally,
|
||||
:term:`PREFERRED_PROVIDERS` is identical to
|
||||
A colon-separated list to determine which recipe should be given
|
||||
preference for cases where multiple recipes provide the same item.
|
||||
Functionally, :term:`PREFERRED_PROVIDERS` is identical to
|
||||
:term:`PREFERRED_PROVIDER`. However, the :term:`PREFERRED_PROVIDERS` variable
|
||||
lets you define preferences for multiple situations using the following
|
||||
form::
|
||||
|
||||
Reference in New Issue
Block a user