From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez+dbus: why glib binding
Date: Tue, 05 Feb 2008 15:13:43 +0100 [thread overview]
Message-ID: <1202220823.15090.88.camel@violet> (raw)
In-Reply-To: <f21e7dc80802042255w4a688071h2678817a45b920fa@mail.gmail.com>
Hi Choi,
> i am intersted to understand why did bluez daemon choose to use the
> glib binding of dbus.
the bluez-utils don't depend on dbus-glib. It is an option that we use
for testing and nothing more.
> i understand it is easier than the low level c library.
>
> but - doesn't glib impose a new depedanbility ?
>
> and - does the bluez daemon use glib for something other than dbus ?
We use glib for the mainloop, the XML parser and other things. However
currently you can configure it to use the included eglib which means you
don't have to depend on glib.
However the option to use eglib will go away with the 4.x series. We
will have hard dependencies on dbus and glib (not dbus-glib).
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-02-05 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 6:55 [Bluez-devel] bluez+dbus: why glib binding Choi Sonim
2008-02-05 14:13 ` Marcel Holtmann [this message]
2008-02-05 14:21 ` Choi Sonim
2008-02-05 14:29 ` Marcel Holtmann
2008-02-05 14:41 ` Choi Sonim
2008-02-05 17:08 ` 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=1202220823.15090.88.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@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