diff options
| author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-06-20 16:48:23 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-06-21 09:19:27 +0100 |
| commit | 17b1507c02c551f6adddb14aca23b309036a601e (patch) | |
| tree | d662f2420d6f6a3b9eeb7a82f588b951626596dd /bitbake | |
| parent | ed4a919cae7b1e03d0cb83636ce88f50a3ca1d16 (diff) | |
| download | poky-17b1507c02c551f6adddb14aca23b309036a601e.tar.gz | |
base.bbclass: Ensure finalised data is displayed in build banner
The build banner displayed at the start of builds can be misleading since
the data store has not been finalised. As easy way to illustrate this is
to use something like:
DEFAULTTUNE = "i586"
DEFAULTTUNE_<machineoverride> = "core2"
and the banner will display the i586 tune yet the core2 tune will be
used. We can avoid this if we finalise a copy of the data before
displaying it.
[YOCTO #4225]
(From OE-Core rev: bdce39f22a0e8c8e1cf237322657220e4201077d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake')
0 files changed, 0 insertions, 0 deletions