summaryrefslogtreecommitdiffstats
path: root/bitbake/doc/bitbake-user-manual
diff options
context:
space:
mode:
authorJacob Kroon <jacob.kroon@gmail.com>2019-09-10 15:43:28 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-09-10 15:18:06 +0100
commit4abf4125f0a098e0cb02700c0412be9a83c514c0 (patch)
tree2ebcdab42b863957da7fb5110571d9cea761ec30 /bitbake/doc/bitbake-user-manual
parent504fa7ee15817b3b4907c489d5c198bd3ca5435b (diff)
downloadpoky-4abf4125f0a098e0cb02700c0412be9a83c514c0.tar.gz
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>
Diffstat (limited to 'bitbake/doc/bitbake-user-manual')
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml8
1 files changed, 3 insertions, 5 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index 6b49d7fa8b..421364c2cf 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -799,17 +799,15 @@
799 <title>Key Expansion</title> 799 <title>Key Expansion</title>
800 800
801 <para> 801 <para>
802 Key expansion happens when the BitBake datastore is finalized 802 Key expansion happens when the BitBake datastore is finalized.
803 just before BitBake expands overrides.
804 To better understand this, consider the following example: 803 To better understand this, consider the following example:
805 <literallayout class='monospaced'> 804 <literallayout class='monospaced'>
806 A${B} = "X" 805 A${B} = "X"
807 B = "2" 806 B = "2"
808 A2 = "Y" 807 A2 = "Y"
809 </literallayout> 808 </literallayout>
810 In this case, after all the parsing is complete, and 809 In this case, after all the parsing is complete,
811 before any overrides are handled, BitBake expands 810 BitBake expands <filename>${B}</filename> into "2".
812 <filename>${B}</filename> into "2".
813 This expansion causes <filename>A2</filename>, which was 811 This expansion causes <filename>A2</filename>, which was
814 set to "Y" before the expansion, to become "X". 812 set to "Y" before the expansion, to become "X".
815 </para> 813 </para>