[oe-commits] [bitbake] 02/02: bitbake-user-manual: key-expansion: Don't refer to overrides
git at git.openembedded.org
git at git.openembedded.org
Tue Sep 10 14:18:34 UTC 2019
This is an automated email from the git hooks/post-receive script.
rpurdie pushed a commit to branch master
in repository bitbake.
commit 218431b0f7c97764cb2c0b79a3aadfe2007f490b
Author: Jacob Kroon <jacob.kroon at gmail.com>
AuthorDate: Tue Sep 10 15:43:28 2019 +0200
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.
Signed-off-by: Jacob Kroon <jacob.kroon at gmail.com>
Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index 6b49d7f..421364c 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -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>
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the Openembedded-commits
mailing list