Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v5 4/4] bluez5: don't exclude from world builds
Date: Mon, 27 Apr 2015 08:13:31 +0100	[thread overview]
Message-ID: <1430118811.13022.91.camel@linuxfoundation.org> (raw)
In-Reply-To: <CABcZAN=Xebt9XPGD_FgpsTp06nbs6OezJhsBNCTnoefCfknxzA@mail.gmail.com>

On Sun, 2015-04-26 at 18:17 -0700, Christopher Larson wrote:
> 
> On Sun, Apr 26, 2015 at 2:57 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>         On Thu, 2015-04-23 at 17:38 +0300, Cristian Iorga wrote:
>         > As BlueZ5 will be the default Bluetooth stack,
>         > don't exclude it from world builds.
>         >
>         > Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
>         > ---
>         >  meta/recipes-connectivity/bluez5/bluez5.inc | 2 --
>         >  1 file changed, 2 deletions(-)
>         >
>         > diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc
>         b/meta/recipes-connectivity/bluez5/bluez5.inc
>         > index 67aafbb..bf845a8 100644
>         > --- a/meta/recipes-connectivity/bluez5/bluez5.inc
>         > +++ b/meta/recipes-connectivity/bluez5/bluez5.inc
>         > @@ -100,5 +100,3 @@ FILES_${PN}-dbg += "\
>         >  RDEPENDS_${PN}-testtools += "python python-dbus
>         python-pygobject"
>         >
>         >  SYSTEMD_SERVICE_${PN} = "bluetooth.service"
>         > -
>         > -EXCLUDE_FROM_WORLD = "1"
>         
>         The reason this is there is to ensure that a bitbake world
>         doesn't build
>         bluez4 and 5 at the same time. Even though v4 is moving to
>         meta-oe, it
>         doesn't change the fact we really need this so world builds
>         don't end up
>         in a mess.
>         
>         Typically, any recipe providing a vritual/xxxx PROVIDES will
>         also end up
>         with an EXCLUDE_FROM_WORLD as the dependency mechanism will
>         then pull in
>         the correct thing(s).
>         
>         Not ideal but its what we have today.
> 
> Originally, world was designed to only build one of any given multiple
> provider situation, IIRC. Is that not the case, or is it the fact that
> both get pulled in via dependencies in a world build, not directly?

I'm not aware of any code that would remove things with multiple
providers from world? Its possible that got lost when we switched to
multiple threads of execution but that was a long time ago.

Cheers,

Richard




  reply	other threads:[~2015-04-27  7:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 14:38 [PATCH v5 0/4] Switch to BlueZ 5.x as default Bluetooth stack Cristian Iorga
2015-04-23 14:38 ` [PATCH v5 1/4] bluez4: add proper systemd support Cristian Iorga
2015-04-23 14:38 ` [PATCH v5 2/4] bluez: remove bluez4 recipes Cristian Iorga
2015-04-23 14:38 ` [PATCH v5 3/4] bitbake.conf: backfill bluez5 feature Cristian Iorga
2015-04-23 14:38 ` [PATCH v5 4/4] bluez5: don't exclude from world builds Cristian Iorga
2015-04-26 21:57   ` Richard Purdie
2015-04-27  1:17     ` Christopher Larson
2015-04-27  7:13       ` Richard Purdie [this message]
2015-04-27 14:17         ` Christopher Larson
2015-04-27 15:14           ` Richard Purdie
2015-04-27 15:27             ` Richard Purdie
2015-04-23 14:48 ` [PATCH v5 0/4] Switch to BlueZ 5.x as default Bluetooth stack Iorga, Cristian

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=1430118811.13022.91.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=clarson@kergoth.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox