<div dir="ltr"> On Jul 18, 2013 9:45 AM, "Tanu Kaskinen" <<a href="mailto:tanu.kaskinen@linux.intel.com" target="_blank">tanu.kaskinen@linux.intel.com</a>> wrote: > > On Fri, 2013-07-12 at 15:06 -0300, <a href="mailto:jprvita@gmail.com" target="_blank">jprvita@gmail.com</a> wrote: > > From: João Paulo Rechi Vita <<a href="mailto:jprvita@openbossa.org" target="_blank">jprvita@openbossa.org</a>> > > > > Support for BlueZ 4 is built only when bluez.pc is present on the target > > system, and that is a big hint that we should load the BlueZ 4 modules. > > On all other cases we can try to load the BlueZ 5 modules. > > --- > > src/daemon/<a href="http://default.pa.in" target="_blank">default.pa.in</a> | 7 ++++++- > > 1 file changed, 6 insertions(+), 1 deletion(-) > > > > diff --git a/src/daemon/<a href="http://default.pa.in" target="_blank">default.pa.in</a> b/src/daemon/<a href="http://default.pa.in" target="_blank">default.pa.in</a> > > index 19dd8a6..9a7fa40 100755 > > --- a/src/daemon/<a href="http://default.pa.in" target="_blank">default.pa.in</a> > > +++ b/src/daemon/<a href="http://default.pa.in" target="_blank">default.pa.in</a> > > @@ -85,15 +85,20 @@ load-module module-jackdbus-detect channels=2 > > .fail > > .endif > > > > -ifelse(@HAVE_BLUEZ_4@, 1, [dnl > > ### Automatically load driver modules for Bluetooth hardware > > .ifexists module-bluetooth-policy@PA_SOEXT@ > > load-module module-bluetooth-policy > > .endif > > I think module-bluetooth-policy should be omitted from the configuration > file if there's no BlueZ support compiled in at all. > I did it this way to avoid having another AC variable just to tell if any BlueZ version is enabled (maybe there is a different way to do it in autotools that I'm not aware of) and since we already check in the .pa language for the existence of module-bluetooth-policy.so. I'll send an updated version and you can comment if there is a better approach. -- João Paulo Rechi Vita <a href="http://about.me/jprvita" target="_blank">http://about.me/jprvita</a> </div>