All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: confused by multiconfig explanation in bitbake manual
Date: Wed, 5 Feb 2020 05:26:34 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.21.2002050523360.1950893@localhost.localdomain> (raw)


  i've never defined a multiconfig build, but this section explaining
it in the BB user manual seems confusing:

///// start

The following statement in the local.conf file both enables BitBake to
perform multiple configuration builds and specifies the two extra
multiconfigs:

     BBMULTICONFIG = "target1 target2"

Once the target configuration files are in place and BitBake has been
enabled to perform multiple configuration builds, use the following
command form to start the builds:

     $ bitbake [mc:multiconfigname:]target [[[mc:multiconfigname:]target] ... ]

Here is an example for two extra multiconfigs: target1 and target2:

     $ bitbake mc::target mc:target1:target mc:target2:target

///// end

  i don't understand the "mc::target" part of that last command, as it
does not seem to be compatible with the definition of the general form
of the command just above that, specifically:

      $ bitbake [mc:multiconfigname:]target ...

can someone clarify this?

rday



             reply	other threads:[~2020-02-05 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 10:26 Robert P. J. Day [this message]
2020-02-05 13:54 ` confused by multiconfig explanation in bitbake manual Joshua Watt
2020-02-05 13:58   ` Robert P. J. Day
2020-02-05 14:01     ` Joshua Watt

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=alpine.LFD.2.21.2002050523360.1950893@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=bitbake-devel@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.