diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-12-20 19:02:11 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-12-22 12:36:40 +0000 |
commit | dbb247cac5fbf7b037e4955f9793828451723924 (patch) | |
tree | 89ea94b1e4e532b92cf75a90b4d617d3ee628820 /README | |
parent | 4fc02c5eaaf7ef70606d06f8c7664ce7e40d166b (diff) | |
download | poky-dbb247cac5fbf7b037e4955f9793828451723924.tar.gz |
bitbake: cookerdata: Convert multiconfig to use BB_CURRENT_MC
People are struggling with multiconfig as the point the conf file
is injected into the data store is not what people expect. We can't
really use a post config since that is too late and we can't really
use a pre config file since that is too early. In OE terms, we need
something right around the local.conf point so it behaves in a similar
way.
A way to handle this is to set the new variable BB_CURRENT_MC to be the
currently selected multiconfig, then the metadata itself can choose
when to inject the approriate configuration.
(Bitbake rev: 518b9015c2be8d3894277a8e54890d6f04d656c0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions