Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Trevor Woerner <twoerner@gmail.com>
Cc: openembedded-architecture
	<openembedded-architecture@lists.openembedded.org>,
	bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: Multi-configuration builds
Date: Fri, 10 Jun 2016 17:13:43 +0100	[thread overview]
Message-ID: <1465575223.13979.188.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160610160710.GA18625@openSUSE-i7.site>

On Fri, 2016-06-10 at 12:07 -0400, Trevor Woerner wrote:
> On Fri 2016-06-10 @ 04:33:29 PM, Richard Purdie wrote:
> > A few people have asked about multi-machine builds.
> 
> Do you envision each config also pointing to individual bblayer
> configurations
> too? I.e. if I'm building for 3 different MACHINEs, with 3 different
> configs
> (local.conf?), then there would also be 3 different bblayers.conf's?


No, there is one local.conf and one bblayers.conf file and then three
different multiconfig files, each one of which sets a different
MACHINE.

Would people really want to support different bblayer files? That would
complicate things quite a lot :/.

Cheers,

Richard


  reply	other threads:[~2016-06-13 10:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10 15:33 Multi-configuration builds Richard Purdie
2016-06-10 16:07 ` Trevor Woerner
2016-06-10 16:13   ` Richard Purdie [this message]
2016-06-13 13:48     ` [Openembedded-architecture] " Otavio Salvador
2016-06-13 14:20       ` Patrick Ohly
2016-06-20  2:46     ` Trevor Woerner
2016-06-20  3:14       ` [Openembedded-architecture] " nick
2016-06-21 13:26         ` Koen Kooi
2016-06-21 18:37           ` nick
2016-06-21 18:48             ` Koen Kooi
2016-06-21 19:18               ` nick

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=1465575223.13979.188.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=twoerner@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox