diff options
| author |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-12-20 19:02:11 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-01-11 17:21:47 +0000 |
| commit | 84b3a5ac3509109abd7550ee8becd3daa8ded0df (patch) | |
| tree | d1fb0e34443d13ac48fd270dfd752caff98dc28f /meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend | |
| parent | 7bab6ffc45494aea9b5c6264a153b3f9b6290301 (diff) | |
| download | openembedded-core-contrib-84b3a5ac3509109abd7550ee8becd3daa8ded0df.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: 1469828fa747da0aaaa3e964954ff17f2b3180fa)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend')
0 files changed, 0 insertions, 0 deletions