[Bluez-users] turning OFF dbus and other extras support?

[Bluez-users] turning OFF dbus and other extras support?

[Andrew Kohlsmith]

It appears that the autoconf process is a little wonky at the present.  Are 
these known issues?

Specifically, autoconf doesn't seem to listen to the negative-versions of 
--enable (i.e. disable support), and the pkg-config output is taken as 
gospel.

I can't disable fuse support with --enable-fuse=no or --disable-fuse (nor 
cups, haven't tried others).  I'm running Slackware 10.2 which does have 
pkg-config, and which does respond correctly.  I did not install bluez-libs 
as a package, but it *is* installed; the environment variable overrides are 
not heeded, so I have to mangle the Makefile or configure script manually to 
get the thing to compile.

I was also hoping that you'd hear my plea for the ability to make dbus support 
*optional* -- I'm using bluez in an embedded system and have to thus stick 
with an older (and non-supported) version.  dbus support adds a LOT of 
additional requirements, including XML, and that's a significant addition to 
any small system.

-A.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] turning OFF dbus and other extras support?

[Marcel Holtmann]

Hi Andrew,

> It appears that the autoconf process is a little wonky at the present.  Are 
> these known issues?
> 
> Specifically, autoconf doesn't seem to listen to the negative-versions of 
> --enable (i.e. disable support), and the pkg-config output is taken as 
> gospel.

the pkg-config part only sets *_found and you need *_enable to actually
activate an optional feature.

> I can't disable fuse support with --enable-fuse=no or --disable-fuse (nor 
> cups, haven't tried others).  I'm running Slackware 10.2 which does have 
> pkg-config, and which does respond correctly.  I did not install bluez-libs 
> as a package, but it *is* installed; the environment variable overrides are 
> not heeded, so I have to mangle the Makefile or configure script manually to 
> get the thing to compile.

You should have. The sample calls for configure can be found in the
README and I simply don't see any problem at the moment. I need some
more input here.

> I was also hoping that you'd hear my plea for the ability to make dbus support 
> *optional* -- I'm using bluez in an embedded system and have to thus stick 
> with an older (and non-supported) version.  dbus support adds a LOT of 
> additional requirements, including XML, and that's a significant addition to 
> any small system.

I am not going to change this back. Otherwise we would have needed a
complete separate protocol and this would have bloated the Bluetooth
code. And the requirement of XML is a myth. It brings its own XML parser
with it.

Regards

Marcel



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] turning OFF dbus and other extras support?

[Andrew Kohlsmith]

On Wednesday 16 August 2006 19:11, Marcel Holtmann wrote:
> the pkg-config part only sets *_found and you need *_enable to actually
> activate an optional feature.

Seems like a weak way to check for a library, but I imagine that only the 
slackware and slackware-derived distros would have this particular issue:

checking pkg-config is at least version 0.9.0... yes
checking for BLUEZ... Package bluez was not found in the pkg-config search 
path.
Perhaps you should add the directory containing `bluez.pc'
to the PKG_CONFIG_PATH environment variable
No package 'bluez' found
configure: error: Bluetooth library is required

$ BLUEZ_CFLAGS=-I~/files/bluez-libs-3.2/include 
BLUEZ_LIBS="-L~/files/bluez-libs/src/.libs -lbluetooth" ./configure

This lets it work, so there's a viable workaround for us old coots.  :-)

> You should have. The sample calls for configure can be found in the
> README and I simply don't see any problem at the moment. I need some
> more input here.

No, I was mistaken here.  I reran the configuration with the command line 
above and pkg-config told the configure script that fuse, openobex and libusb 
weren't found, but let it build regardless.

> I am not going to change this back. Otherwise we would have needed a
> complete separate protocol and this would have bloated the Bluetooth
> code. And the requirement of XML is a myth. It brings its own XML parser
> with it.

A complete separate protocol to do what?  v2.25 seems to get by fine without a 
notification subsystem.

Regarding dbus and an xml requirement -- the dbus wiki page seems to disagree 
with you on this.  From http://www.freedesktop.org/wiki/Software/dbus:

"D-Bus' only *required* dependency is an XML parser (either libxml or expat)."

I will make another attempt at building dbus and bluez-3.2 under my embedded 
environment.  I may have been overly impatient in trying to get it to work.

-A.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] turning OFF dbus and other extras support?

[Marcel Holtmann]

Hi Andrew,

> > the pkg-config part only sets *_found and you need *_enable to actually
> > activate an optional feature.
> 
> Seems like a weak way to check for a library, but I imagine that only the 
> slackware and slackware-derived distros would have this particular issue:
> 
> checking pkg-config is at least version 0.9.0... yes
> checking for BLUEZ... Package bluez was not found in the pkg-config search 
> path.
> Perhaps you should add the directory containing `bluez.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'bluez' found
> configure: error: Bluetooth library is required
> 
> $ BLUEZ_CFLAGS=-I~/files/bluez-libs-3.2/include 
> BLUEZ_LIBS="-L~/files/bluez-libs/src/.libs -lbluetooth" ./configure
> 
> This lets it work, so there's a viable workaround for us old coots.  :-)

you might wanna try to set PKG_CONFIG_PATH to make it find the needed
bluez.pc file. Check "man pkg-config" for more details.

> > You should have. The sample calls for configure can be found in the
> > README and I simply don't see any problem at the moment. I need some
> > more input here.
> 
> No, I was mistaken here.  I reran the configuration with the command line 
> above and pkg-config told the configure script that fuse, openobex and libusb 
> weren't found, but let it build regardless.

If these libraries are not found, none of them get build. You might see
make entering these subdirectories, but that's it.

> > I am not going to change this back. Otherwise we would have needed a
> > complete separate protocol and this would have bloated the Bluetooth
> > code. And the requirement of XML is a myth. It brings its own XML parser
> > with it.
> 
> A complete separate protocol to do what?  v2.25 seems to get by fine without a 
> notification subsystem.

It is more than simple notification thingy. You can control all needed
functionality. And this is why it is 3.x now and no longer 2.x.

> Regarding dbus and an xml requirement -- the dbus wiki page seems to disagree 
> with you on this.  From http://www.freedesktop.org/wiki/Software/dbus:
> 
> "D-Bus' only *required* dependency is an XML parser (either libxml or expat)."

Then go with expat. It is small and lightweight.

> I will make another attempt at building dbus and bluez-3.2 under my embedded 
> environment.  I may have been overly impatient in trying to get it to work.

Nobody said, that it is easy, but even the Nokia 770 for example is
happy with D-Bus and I know that a lot of embedded people actually use
D-Bus instead inventing a message bus over and over.

Regards

Marcel



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users