Skip to contentSkip to conversation

Bluez5 fixes

PATCH In review Mihai Prica 2 participants 4 messages Sep 6, 2013

lore
Share & tools
lore
#0 lore raw

cover Bluez5 fixes

The following changes since commit c7994f83baa678a4670472e1f037bfc16cb1e3be:

bitbake: runqueue: Fix scenequeue to pass file descriptors, not a float (2013-09-02 09:16:24 +0100)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib mihaip/bluez5
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mihaip/bluez5

Mihai Prica (2):
bluez5: Install the bluetooth library
bluez5: Rename tests package to testtools

 meta/recipes-connectivity/bluez5/bluez5.inc |    7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)
Signature · 1 line
1.7.9.5
#1 lore raw

PATCH 1/2 bluez5: Install the bluetooth library

Bluez5 doesn't install libbluetooth by default. This is required by connman, ofono or other packages.

---
 meta/recipes-connectivity/bluez5/bluez5.inc |    1 +
 1 file changed, 1 insertion(+)
meta/recipes-connectivity/bluez5/bluez5.inc +1 -0
index 2fae7fb..e2b7169 100644
@@ -36,6 +36,7 @@ EXTRA_OECONF = "\
   --enable-test \
   --enable-datafiles \
   ${@base_contains('DISTRO_FEATURES', 'systemd', '--with-systemdunitdir=${systemd_unitdir}/system/', '--disable-systemd', d)} \
+  --enable-library \
 "
 
 do_install_append() {
Signature · 1 line
1.7.9.5
#2 lore raw

PATCH 2/2 bluez5: Rename tests package to testtools

In reply to Mihai Prica

Bluez5 ships some tools that can be used to test its functionality.

The installation can be tested using "make check" and this should be included in a ptest package.

[YB #5028]

---
 meta/recipes-connectivity/bluez5/bluez5.inc |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
meta/recipes-connectivity/bluez5/bluez5.inc +4 -2
index e2b7169..e5cb9e8 100644
@@ -55,7 +55,7 @@ do_install_append() {
 }
 
 ALLOW_EMPTY_libasound-module-bluez = "1"
-PACKAGES =+ "libasound-module-bluez ${PN}-test ${PN}-obex"
+PACKAGES =+ "libasound-module-bluez ${PN}-testtools ${PN}-obex"
 
 FILES_libasound-module-bluez = "${libdir}/alsa-lib/lib*.so ${datadir}/alsa"
 FILES_${PN} += "${libdir}/bluetooth/plugins ${libdir}/bluetooth/plugins/*.so ${base_libdir}/udev/ ${nonarch_base_libdir}/udev/ ${systemd_unitdir}/ ${datadir}/dbus-1"
@@ -70,7 +70,7 @@ FILES_${PN}-obex = "${libdir}/bluez5/bluetooth/obexd \
                    "
 SYSTEMD_SERVICE_${PN}-obex = "obex.service"
 
-FILES_${PN}-test = "${libdir}/bluez/test/*"
+FILES_${PN}-testtools = "${libdir}/bluez/test/*"
 
 FILES_${PN}-dbg += "\
   ${libdir}/${BPN}/bluetooth/.debug \
@@ -79,4 +79,6 @@ FILES_${PN}-dbg += "\
   */udev/.debug \
   "
 
+RDEPENDS_${PN}-testtools += "python python-dbus python-pygobject"
+
 SYSTEMD_SERVICE_${PN} = "bluetooth.service"
Signature · 1 line
1.7.9.5
#3 lore raw

Re: [PATCH 2/2] bluez5: Rename tests package to testtools

Quoted 27 lines · Mihai Prica

Bluez5 ships some tools that can be used to test its functionality.

The installation can be tested using "make check" and this should be included in a ptest package.

[YB #5028]

---
  meta/recipes-connectivity/bluez5/bluez5.inc |    6 ++++--
  1 file changed, 4 insertions(+), 2 deletions(-)
meta/recipes-connectivity/bluez5/bluez5.inc +1 -1
index e2b7169..e5cb9e8 100644
@@ -55,7 +55,7 @@ do_install_append() {
  }
 
  ALLOW_EMPTY_libasound-module-bluez = "1"
-PACKAGES =+ "libasound-module-bluez ${PN}-test ${PN}-obex"
+PACKAGES =+ "libasound-module-bluez ${PN}-testtools ${PN}-obex"
 
  FILES_libasound-module-bluez = "${libdir}/alsa-lib/lib*.so ${datadir}/alsa"
  FILES_${PN} += "${libdir}/bluetooth/plugins ${libdir}/bluetooth/plugins/*.so ${base_libdir}/udev/ ${nonarch_base_libdir}/udev/ ${systemd_unitdir}/ ${datadir}/dbus-1"

meta/recipes-connectivity/bluez5/bluez5.inc FILES_${PN}-obex = "${libdir}/bluez5/bluetooth/obexd \ · line 74

Quoted 6 lines
meta/recipes-connectivity/bluez5/bluez5.inc +1 -1
@@ -70,7 +70,7 @@ FILES_${PN}-obex = "${libdir}/bluez5/bluetooth/obexd \
                     "
  SYSTEMD_SERVICE_${PN}-obex = "obex.service"
 
-FILES_${PN}-test = "${libdir}/bluez/test/*"
+FILES_${PN}-testtools = "${libdir}/bluez/test/*"
 

Are all the files located in test related to the testtools or are some of them related to ptest?

Sau!

Quoted 10 lines
meta/recipes-connectivity/bluez5/bluez5.inc +2 -0
  FILES_${PN}-dbg += "\
    ${libdir}/${BPN}/bluetooth/.debug \
@@ -79,4 +79,6 @@ FILES_${PN}-dbg += "\
    */udev/.debug \
    "
 
+RDEPENDS_${PN}-testtools += "python python-dbus python-pygobject"
+
  SYSTEMD_SERVICE_${PN} = "bluetooth.service"