bitbake: bitbake-user-manual-metadata.rst: OE_BUILTIN_FRAGMENTS -> OE_FRAGMENTS_BUILTIN

The actual variable name used in oe-core is OE_FRAGMENTS_BUILTIN,
which is in a consistent format with other OE_FRAGMENTS_XXX vars.

(Bitbake rev: 86c5f6aa59980d04264bc526976a49fdf749d1af)

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Chen Qi
2025-10-27 15:26:20 +08:00
committed by Richard Purdie
parent 249793af75
commit 1effe32357

View File

@@ -999,7 +999,7 @@ This directive allows fine-tuning local configurations with configuration
snippets contained in layers in a structured, controlled way. Typically it would
go into ``bitbake.conf``, for example::
addfragments conf/fragments OE_FRAGMENTS OE_FRAGMENTS_METADATA_VARS OE_BUILTIN_FRAGMENTS
addfragments conf/fragments OE_FRAGMENTS OE_FRAGMENTS_METADATA_VARS OE_FRAGMENTS_BUILTIN
``addfragments`` takes four parameters:
@@ -1040,7 +1040,7 @@ each other when several fragments are enabled.
The variable containing a built-in fragment definitions could look like this::
OE_BUILTIN_FRAGMENTS = "someprefix:SOMEVARIABLE anotherprefix:ANOTHERVARIABLE"
OE_FRAGMENTS_BUILTIN = "someprefix:SOMEVARIABLE anotherprefix:ANOTHERVARIABLE"
and then if 'someprefix/somevalue' is added to the variable that holds the list
of enabled fragments: