Skip to contentSkip to conversation

bitbake-user-manual: Correct description for _append/_prepend/_remove

PATCH New Jacob Kroon 1 participant 2 messages Sep 10, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 bitbake-user-manual: Correct description for _append/_prepend/_remove

The effects of _append/_prepend/_remove are applied when a variable is expanded, not after parsing has completed.

---
 doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)
doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +3 -4
index 88622421..6b49d7fa 100644
@@ -369,9 +369,8 @@
 
             <para>
                 These operators differ from the ":=", ".=", "=.", "+=", and "=+"
-                operators in that their effects are deferred
-                until after parsing completes rather than being immediately
-                applied.
+                operators in that their effects are applied at variable
+                expansion time rather than being immediately applied.
                 Here are some examples:
                 <literallayout class='monospaced'>
      B = "bval"
@@ -435,7 +434,7 @@
 
             <para>
                 Like "_append" and "_prepend", "_remove"
-                is deferred until after parsing completes.
+                is applied at variable expansion time.
             </para>
         </section>
 
Signature · 1 line
2.21.0
#1 lore raw

PATCH 2/2 bitbake-user-manual: key-expansion: Don't refer to overrides

Nowadays bitbake applies overrides dynamically, not at a single specific point in time during parsing.

---
 doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)
doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +3 -5
index 6b49d7fa..421364c2 100644
@@ -799,17 +799,15 @@
             <title>Key Expansion</title>
 
             <para>
-                Key expansion happens when the BitBake datastore is finalized
-                just before BitBake expands overrides.
+                Key expansion happens when the BitBake datastore is finalized.
                 To better understand this, consider the following example:
                 <literallayout class='monospaced'>
      A${B} = "X"
      B = "2"
      A2 = "Y"
                 </literallayout>
-                In this case, after all the parsing is complete, and
-                before any overrides are handled, BitBake expands
-                <filename>${B}</filename> into "2".
+                In this case, after all the parsing is complete,
+                BitBake expands <filename>${B}</filename> into "2".
                 This expansion causes <filename>A2</filename>, which was
                 set to "Y" before the expansion, to become "X".
             </para>
Signature · 1 line
2.21.0