From: Patrick Ohly <patrick.ohly@intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Multi-configuration builds
Date: Mon, 13 Jun 2016 16:20:26 +0200 [thread overview]
Message-ID: <1465827626.28632.31.camel@intel.com> (raw)
In-Reply-To: <CAP9ODKrXpD1RC2AVxqszvkM3MZsQ-1dU=BNO4DNzGgCg8k+avw@mail.gmail.com>
On Mon, 2016-06-13 at 10:48 -0300, Otavio Salvador wrote:
> > Would people really want to support different bblayer files? That would
> > complicate things quite a lot :/.
>
> The multi configuration should imply same metadata setup; for
> different things people need to use different builddirs.
I agree. Using the same set of layers is sometimes a bit painful to
achieve when BSP layers assume that merely adding the layer is supposed
to modify the resulting build, regardless which MACHINE is selected, but
that's a problem that should be fixed in those BSP layers.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2016-06-13 14:20 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
2016-06-13 13:48 ` [Openembedded-architecture] " Otavio Salvador
2016-06-13 14:20 ` Patrick Ohly [this message]
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=1465827626.28632.31.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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