bitbake: 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.

(Bitbake rev: 218431b0f7c97764cb2c0b79a3aadfe2007f490b)

Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Jacob Kroon authored and Richard Purdie committed 2019-09-10 15:18:06 +01:00
1 parent 504fa7ee15
commit 4abf4125f0
1 file changed
+3 -5
@@ -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>