From: Andrew Kohlsmith <akohlsmith-bluez@benshaw.com>
To: bluez-users@lists.sourceforge.net
Date: Wed, 16 Aug 2006 22:08:37 -0400
References: <200608161159.35033.akohlsmith-bluez@benshaw.com>
	<1155769899.4075.95.camel@aeonflux.holtmann.net>
In-Reply-To: <1155769899.4075.95.camel@aeonflux.holtmann.net>
MIME-Version: 1.0
Message-Id: <200608162208.37986.akohlsmith-bluez@benshaw.com>
Subject: Re: [Bluez-users] turning OFF dbus and other extras support?
Reply-To: BlueZ users <bluez-users@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-users-bounces@lists.sourceforge.net
Errors-To: bluez-users-bounces@lists.sourceforge.net

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