From: Andreas Oberritter <obi@opendreambox.org>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: Splitting meta-oe?
Date: Wed, 21 Feb 2018 20:33:52 +0100 [thread overview]
Message-ID: <20180221203352.55cd9a96@t460p> (raw)
In-Reply-To: <1519225097.6698.8.camel@intel.com>
On Wed, 21 Feb 2018 15:58:17 +0100
Patrick Ohly <patrick.ohly@intel.com> wrote:
> On Wed, 2018-02-21 at 14:14 +0000, Burton, Ross wrote:
> > > But that kind of mechanism seems highly prone to breakage and
> > > likely to
> > > be highly contentious even if it was shown to be reliable, so it
> > > may not
> > > get beyond a "that'd be nice" thing for me.
> > >
> > > Unless someone else has already implemented it and I'm just not
> > > aware of
> > > how to use it? :-)
> > >
> >
> > meta-freescale (iirc) does this, conditionally adds
> > sub-layers to BBLAYERS based on what other layers are already
> > enabled.
>
> The approach used by meta-freescale works with older releases.
> BBFILES_DYNAMIC [1] (supported by bitbake 1.36/Yocto 2.4) is a bit more
> robust.
>
> [1] https://patchwork.openembedded.org/patch/140532/
>
That's interesting. Is it possible to express dependencies on more than one
layer for a group of recipes with this mechanism?
Regards,
Andreas
next prev parent reply other threads:[~2018-02-21 19:33 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 10:45 Splitting meta-oe? Burton, Ross
2018-02-20 14:15 ` Joe MacDonald
2018-02-20 16:50 ` akuster808
2018-02-20 17:13 ` Bruce Ashfield
2018-02-20 18:52 ` Khem Raj
2018-02-21 0:51 ` Bruce Ashfield
2018-02-21 8:49 ` Martin Jansa
2018-02-21 9:06 ` Martin Jansa
2018-02-21 9:48 ` Andrea Adami
2018-02-21 10:22 ` Martin Jansa
2018-02-21 14:02 ` Joe MacDonald
2018-02-21 14:14 ` Burton, Ross
2018-02-21 14:58 ` Patrick Ohly
2018-02-21 15:01 ` Otavio Salvador
2018-02-21 19:33 ` Andreas Oberritter [this message]
2018-02-22 9:18 ` Patrick Ohly
2018-02-21 14:20 ` Tom Rini
2018-02-21 14:44 ` Joe MacDonald
2018-02-21 13:34 ` Bruce Ashfield
2018-02-21 13:38 ` Bruce Ashfield
2018-02-21 13:45 ` Joe MacDonald
2018-02-21 13:55 ` Bruce Ashfield
2018-02-21 13:59 ` Otavio Salvador
2018-02-20 17:46 ` Richard Purdie
2018-02-20 18:00 ` Tim Orling
2018-02-20 18:28 ` Martin Jansa
2018-02-20 18:40 ` Khem Raj
2018-02-20 18:52 ` Richard Purdie
2018-02-20 19:15 ` Khem Raj
2018-02-20 21:55 ` Richard Purdie
2018-02-20 22:27 ` Martin Jansa
2018-02-20 23:17 ` Andreas Müller
2018-02-20 23:41 ` Richard Purdie
2018-03-17 3:50 ` Trevor Woerner
2018-03-17 14:23 ` Philip Balister
2018-03-18 5:49 ` Trevor Woerner
2018-02-21 0:07 ` Otavio Salvador
2018-02-21 0:10 ` Otavio Salvador
2018-02-21 13:57 ` Tom Rini
2018-02-21 14:00 ` Otavio Salvador
2018-02-21 14:48 ` Tom Rini
2018-02-21 14:09 ` Martin Hundebøll
2018-02-22 6:53 ` Jonas Bonn
2018-02-22 9:27 ` Patrick Ohly
2018-02-22 9:40 ` Otavio Salvador
2018-02-21 15:54 ` Patrick Ohly
2018-02-20 20:32 ` akuster808
2018-02-20 19:06 ` Khem Raj
2018-02-20 16:54 ` Vesa Jääskeläinen
2018-02-20 18:49 ` Khem Raj
2018-02-28 17:17 ` Alexander Kanavin
2018-02-28 21:33 ` Andreas Müller
2018-03-01 1:20 ` akuster808
2018-03-01 8:46 ` Alexander Kanavin
2018-03-01 1:17 ` akuster808
2018-03-01 9:04 ` Alexander Kanavin
2018-03-01 18:44 ` akuster808
2018-03-01 18:46 ` Alexander Kanavin
2018-03-01 22:11 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2017-02-17 17:07 Burton, Ross
2017-02-17 17:24 ` Andreas Müller
2017-02-17 18:02 ` Martin Jansa
2017-02-17 18:28 ` Joe MacDonald
2017-02-17 19:45 ` Philip Balister
2017-02-20 3:31 ` Richard Purdie
2017-02-20 4:28 ` Joe MacDonald
2017-02-20 11:18 ` Martin Jansa
2017-02-22 16:15 ` akuster808
2017-02-17 20:54 ` Andreas Müller
2017-02-18 21:35 ` Burton, Ross
2017-02-17 21:55 ` akuster808
2017-02-18 0:53 ` Khem Raj
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=20180221203352.55cd9a96@t460p \
--to=obi@opendreambox.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=patrick.ohly@intel.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 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.