diff options
| author |   Jacob Kroon <jacob.kroon@gmail.com> | 2019-09-10 15:43:28 +0200 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-09-10 15:17:58 +0100 |
| commit | 218431b0f7c97764cb2c0b79a3aadfe2007f490b (patch) | |
| tree | 52f21e253b242d967e263bcb07e099e237cc569d | |
| parent | f9b67433cb4fe5132ab2cf4a9c6bc078b42e1960 (diff) | |
| download | bitbake-218431b0f7c97764cb2c0b79a3aadfe2007f490b.tar.gz | |
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@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 8 |
1 files 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 6b49d7fa8..421364c2c 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> |