From: Cristian Iorga <cristian.iorga@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 09/11] conf/distro/include/default-providers: updated bluez-hcidump providers
Date: Mon, 16 Feb 2015 17:06:19 +0200 [thread overview]
Message-ID: <a56cd359d1083006ecb6e0eb25f8a0066c797f45.1424098977.git.cristian.iorga@intel.com> (raw)
In-Reply-To: <cover.1424098977.git.cristian.iorga@intel.com>
In-Reply-To: <cover.1424098977.git.cristian.iorga@intel.com>
If BlueZ5 is added to a build as a replacement for BlueZ4,
the provider for bluez-hcidump will be bluez5.
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
---
meta/conf/distro/include/default-providers.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/distro/include/default-providers.inc b/meta/conf/distro/include/default-providers.inc
index 4dc42a7..25118fa 100644
--- a/meta/conf/distro/include/default-providers.inc
+++ b/meta/conf/distro/include/default-providers.inc
@@ -44,7 +44,7 @@ PREFERRED_PROVIDER_udev ?= "${@bb.utils.contains('DISTRO_FEATURES','systemd','sy
# There are issues with runtime packages and PREFERRED_PROVIDER, see YOCTO #5044 for details
# on this rather strange entry.
PREFERRED_PROVIDER_bluez4 ?= "bluez4"
-PREFERRED_PROVIDER_bluez-hcidump ?= "bluez-hcidump"
+PREFERRED_PROVIDER_bluez-hcidump ?= "${@bb.utils.contains('DISTRO_FEATURES','bluetooth bluez5','bluez5','bluez-hcidump',d)}"
# Alternative is ltp-ddt in meta-oe: meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb
PREFERRED_PROVIDER_ltp ?= "ltp"
PREFERRED_PROVIDER_getopt ?= "util-linux-getopt"
--
2.1.0
next prev parent reply other threads:[~2015-02-16 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 15:06 [PATCH 00/11] BlueZ 5 as bluetooth alternative stack Cristian Iorga
2015-02-16 15:06 ` [PATCH 01/11] bluetooth.bbclass: simplify recipe inference of bluetooth provider Cristian Iorga
2015-02-16 15:06 ` [PATCH 02/11] packagegroup-base: select distro preference for bluez provider Cristian Iorga
2015-02-16 15:06 ` [PATCH 03/11] pulseaudio: " Cristian Iorga
2015-02-16 15:06 ` [PATCH 04/11] qt-mobility: " Cristian Iorga
2015-02-16 15:06 ` [PATCH 05/11] neard: " Cristian Iorga
2015-02-16 15:06 ` [PATCH 06/11] libpcap: " Cristian Iorga
2015-02-16 15:06 ` [PATCH 07/11] ofono: " Cristian Iorga
2015-02-16 15:06 ` [PATCH 08/11] gstreamer1.0-plugins-bad: " Cristian Iorga
2015-02-16 15:06 ` Cristian Iorga [this message]
2015-02-16 15:06 ` [PATCH 10/11] connman: depend on distro provider of bluez Cristian Iorga
2015-02-16 15:06 ` [PATCH 11/11] default-providers: Set the preferred provider for bluez based on version Cristian Iorga
2015-02-17 12:17 ` [PATCH 00/11] BlueZ 5 as bluetooth alternative stack Peter A. Bigot
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=a56cd359d1083006ecb6e0eb25f8a0066c797f45.1424098977.git.cristian.iorga@intel.com \
--to=cristian.iorga@intel.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 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.