All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Watt <jpewhacker@gmail.com>
To: Bryan Evenson <bevenson@melinkcorp.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] multiconfig: Build breaks parsing recipes for other config layer
Date: Mon, 27 Feb 2023 15:03:48 -0600	[thread overview]
Message-ID: <fb887f22-01c3-e202-18f4-f0c499c4d3d1@gmail.com> (raw)
In-Reply-To: <CH0PR20MB4122DCF26110929D2A178451BBAF9@CH0PR20MB4122.namprd20.prod.outlook.com>


On 2/27/23 14:35, Bryan Evenson wrote:
> I'm testing a new board with a BSP that is setup on the gatesgarth branch.  I've been able to build and load the demo images for this board.  I'm now trying to use multiconfig to build images for my old board and my new board.  So far the build hasn't got past parsing recipes and I'm wondering what I'm doing wrong.
>
> For my setup, I have two separate layers for the two different boards.  Each layer has its own MACHINE and DISTRO definitions.  I setup the multiconfig files as follows:
>
> conf/local.conf:
> Added the following line:
> BBMULTICONFIG = "configA configB"
>
> conf/multiconfig/configA.conf: (config for old board)
> MACHINE = "machineA"
> TMPDIR = "${TOPDIR}/tmpConfigA"
> DISTRO = "distroA"
>
> conf/multiconfig/configB.conf: (config for new board)
> MACHINE = "machineB"
> TMPDIR = "${TOPDIR}/tmpConfigB"
> DISTRO = "distroB"
>
> If I try building the old image by doing:
> bitbake mc:configA:image-nameA
>
> I get errors while parsing the files.  It complains about a Network Manager bbappend in layer B that uses variables that depends on MACHINE being set to "machineB".  The image for configA does not use Network Manager.  I also tried removing the MACHINE and DISTRO settings from local.conf to make sure the multiconfig settings are used, but then I get an error that MACHINE has not been set.
>
> Does layerB need something added to it so parsing ignores recipes in this layer when they aren't needed?  Or do the recipes need to change so they build for other machines?

When you use multiconfig, all of you layers need to parse for all 
configurations (although this is generally good layer practice in 
general, not just when using multiconfig). Usually this involves writing 
the recipes to use overrides where appropriate


Although, if you _really_ don't want to do that, the BBMASK variable 
(https://docs.yoctoproject.org/ref-manual/variables.html#term-BBMASK) 
can now be set per-multiconfig so you can have layerA mask out layerB 
recipes and vice-versa.

>
> Thanks,
> Bryan
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#177808): https://lists.openembedded.org/g/openembedded-core/message/177808
> Mute This Topic: https://lists.openembedded.org/mt/97276005/3616693
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [JPEWhacker@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


  reply	other threads:[~2023-02-27 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 20:35 multiconfig: Build breaks parsing recipes for other config layer Bryan Evenson
2023-02-27 21:03 ` Joshua Watt [this message]
2023-02-28  7:06   ` [OE-core] " Mikko Rapeli
2023-02-28 13:43     ` Bryan Evenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb887f22-01c3-e202-18f4-f0c499c4d3d1@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=bevenson@melinkcorp.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.