public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Cc: bluez-users@lists.sf.net
Subject: Re: [Bluez-users] turning OFF dbus and other extras support?
Date: Thu, 17 Aug 2006 01:11:39 +0200	[thread overview]
Message-ID: <1155769899.4075.95.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <200608161159.35033.akohlsmith-bluez@benshaw.com>

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

  reply	other threads:[~2006-08-16 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 15:59 [Bluez-users] turning OFF dbus and other extras support? Andrew Kohlsmith
2006-08-16 23:11 ` Marcel Holtmann [this message]
2006-08-17  2:08   ` Andrew Kohlsmith
2006-08-17 12:43     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1155769899.4075.95.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sf.net \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox