buildroot/package/bluez5_utils, branch 2019.02-op-build

bluez5_utils: fix build with pkgconf 1.5.3

2018-12-13T20:22:17+00:00

Since the bump to 1.5.3, pkgconf prepends the sysroot to all absolute paths found in the .pc file. This is correct when the paths refer to something in STAGING_DIR (e.g. libdir, includedir), but not when it refers to something used for the target. bluez5_utils uses the sysconfdir variable from dbus-1.pc to decide where to install things. Since DESTDIR is prepended to the install destination, this will end up in the wrong location. Until a better solution is found in pkgconf, pass the sysconfdir to use explicitly instead of relying on dbus-1.pc. Fixes: - http://autobuild.buildroot.org/results/498e7e368fbb3d69c2f311e3e5bc213e507b8023 Signed-off-by: Fabrice Fontaine Signed-off-by: Thomas Petazzoni

package/bluez5_utils: ensure build order with the headers-only variant

2018-10-21T16:28:13+00:00

Since bluez5_utils and bluez5_utils-headers would install the same set of files (headers), we want to ensure the former is run after the latter. Signed-off-by: "Yann E. MORIN" Cc: Grzegorz Blach Cc: Arnout Vandecappelle Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

bluez5_utils-headers: new package

2018-10-21T15:35:31+00:00

Header files from bluez utils version 5.x. Separated headers are required to break circular dependencies when python3 is built with bluetooth support. This is a blind option, it will be automatically selected by python3 when bluez5_utils is enabled. Signed-off-by: Grzegorz Blach [Arnout: add comment to keep versions in sync; make it a blind option] Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

bluez5_utils: bump to version 5.50

2018-06-19T20:14:46+00:00

Drop upstream patch and remove `AUTORECONF = YES`. Signed-off-by: Jörg Krause Signed-off-by: Peter Korsgaard

bluez5_utils: rename options to have the proper suffix

2018-05-21T21:05:07+00:00

The bluez5_utils Config.in options had a bogus prefix: BR2_PACKAGE_BLUEZ5 instead of the expected BR2_PACKAGE_BLUEZ5_UTILS. This commit fixes that, and adds the appropriate Config.in.legacy handling. Signed-off-by: Thomas Petazzoni Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

bluez5_utils: add patch to fix readline issue

2018-04-21T12:53:01+00:00

Since bluez5_utils 5.49, some code using readline was compiled even if readline was not available. After this issue was reported upstream, a patch was proposed by an upstream developer to address the issue. This commit integrates this patch (under review upstream), which fixes the problem. Fixes: http://autobuild.buildroot.net/results/3e266a79acab8b8eb33360f7afbc1cd6db46f7cb/ Signed-off-by: Thomas Petazzoni

bluez5_utils: bump to version 5.49

2018-03-16T09:35:16+00:00

Drop musl patch, which is not necessary anymore as netinet vs linux header clash is fixed. Also add hash for the license files. musl build successfully tested with: * armv7-eabihf--musl--stable-2017.05-toolchains-1-1 (GCC 5.4.0, Linux headers 3.10.105, musl 1.1.16) * armv7-eabihf--musl--bleeding-edge-2018.02-1 (GCC 7.3.0, Linux headers 4.9.80, musl 1.1.18) Signed-off-by: Jörg Krause Signed-off-by: Peter Korsgaard

bluez5_utils: Make systemd link correctly

2018-02-27T21:44:17+00:00

The link in /etc/systemd/system/, named dbus-org.bluez.service, pointing to ../../../../usr/lib/systemd/system/bluetooth.service has one too many ".." in it. Likely the target was copied from the other link in /etc/systemd/system/bluetooth.target.wants/, which is one level deeper. Adjust link to be correct. Signed-off-by: Trent Piepho Reviewed-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

package/bluez5_utils: bump version to 5.48

2018-01-07T14:06:53+00:00

Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

bluez5_utils: define FIRMWARE_DIR for hciattach_bcm43xx

2017-10-22T14:59:22+00:00

The tool hciattach_bcm43xx defines the default firmware path in `/etc/firmware`, but the Broadcom firmware blobs are usually stored in `/lib/firmware`. Signed-off-by: Jörg Krause Signed-off-by: Thomas Petazzoni