Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/1] bluez4: drop usbpath from DEPENDS
Date: Fri, 19 Aug 2011 15:30:33 -0700	[thread overview]
Message-ID: <f22710e02b075d0cac9eb153e054e0c18905907d.1313792370.git.josh@linux.intel.com> (raw)
In-Reply-To: <cover.1313792370.git.josh@linux.intel.com>
In-Reply-To: <cover.1313792370.git.josh@linux.intel.com>

We don't (currently) have usbpath in oe-core, so drop it from the DEPENDS to
make BlueZ buildable again.

Signed-off-by: Joshua Lock <josh@linux.intel.com>
CC: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta/recipes-connectivity/bluez/bluez4_4.96.bb |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta/recipes-connectivity/bluez/bluez4_4.96.bb b/meta/recipes-connectivity/bluez/bluez4_4.96.bb
index edba167..994cec7 100644
--- a/meta/recipes-connectivity/bluez/bluez4_4.96.bb
+++ b/meta/recipes-connectivity/bluez/bluez4_4.96.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e \
                     file://COPYING.LIB;md5=fb504b67c50331fc78734fed90fb0e09 \
                     file://src/main.c;beginline=1;endline=24;md5=9bc54b93cd7e17bf03f52513f39f926e \
                     file://sbc/sbc.c;beginline=1;endline=25;md5=1a40781ed30d50d8639323a184aeb191"
-DEPENDS = "udev gst-plugins-base alsa-lib libusb dbus-glib usbpath"
+DEPENDS = "udev gst-plugins-base alsa-lib libusb dbus-glib"
 RDEPENDS_${PN}-dev = "bluez-hcidump"
 
 ASNEEDED = ""
-- 
1.7.6




  reply	other threads:[~2011-08-19 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 22:30 [PATCH 0/1] Fix building BlueZ Joshua Lock
2011-08-19 22:30 ` Joshua Lock [this message]
2011-08-19 22:42   ` [PATCH 1/1] bluez4: drop usbpath from DEPENDS Richard Purdie

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=f22710e02b075d0cac9eb153e054e0c18905907d.1313792370.git.josh@linux.intel.com \
    --to=josh@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox