Skip to content
Snippets Groups Projects
Select Git revision
  • 84b3a5ac3509109abd7550ee8becd3daa8ded0df
  • stboot default
  • stbootv2
  • master protected
  • scarthgap-5.0
  • yocto-5.0
  • yocto-4.3.4
  • nanbield-4.3.4
  • yocto-4.0.17
  • kirkstone-4.0.17
  • 5.0_M3
  • dunfell-23.0.32
  • yocto-3.1.32
  • nanbield-4.3.3
  • yocto-4.3.3
  • yocto-4.0.16
  • kirkstone-4.0.16
  • yocto-3.1.31
  • dunfell-23.0.31
  • 5.0_M2
  • yocto-4.3.2
  • nanbield-4.3.2
  • 5.0_M1
  • yocto-4.0.15
24 results

yocto-poky

user avatar
bitbake: cookerdata: Convert multiconfig to use BB_CURRENT_MC
Richard Purdie authored 
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: default avatarRichard Purdie <richard.purdie@linuxfoundation.org>
84b3a5ac
History
user avatar 84b3a5ac
History
Name Last commit Last update