On Wed, 2014-08-06 at 16:04 +0800, Cho, Yu-Chen wrote:
From BlueZ 5.0 , dbus API org.bluez.Serial has been removed and others have changed. So add option "--disable-bluez5" for applet to get bluetooth DUN (Dial-Up Networking) support on BlueZ 4.X and remove it when using BlueZ 5.x.(Default is disable Bluez 5) Signed-off-by: Cho, Yu-Chen <acho suse com> --- configure.ac | 14 ++++++++++++++ src/gnome-bluetooth/bt-widget.c | 6 ++++++ src/gnome-bluetooth/nma-bt-device.c | 8 ++++++++ 3 files changed, 28 insertions(+) diff --git a/configure.ac b/configure.ac index d6ca9e6..857f0ca 100644 --- a/configure.ac +++ b/configure.ac @@ -128,6 +128,20 @@ AC_SUBST(GTK_CFLAGS) AC_SUBST(GTK_LIBS) GTK_CFLAGS="$GTK_CFLAGS -DGDK_VERSION_MIN_REQUIRED=GDK_VERSION_3_4" + +#### BlueZ 5 support #### + +AC_ARG_WITH([bluz5], + AS_HELP_STRING([--enable-bluez5|--disable-bluez5], [Enable Bluez 5 support]), + enable_bluez5="$withval") + +if (test "x$enable_bluez5" == "xyes");then + AC_DEFINE([HAVE_BLUEZ_5], 1, [Enable blueZ 5 support]) +else + AC_DEFINE([HAVE_BLUEZ_5], 0, [Disable blueZ 5 support])
shouldn't nowadays bluez5 be default? How about trying to detect bluez5 headers ... the default should then be what was detected. And specifying --enable-bluez5 fails if it cannot detect having support. Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part