From: "Voni Hakau" <hakauvoni@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] bluez-utils dependencies
Date: Wed, 23 May 2007 08:54:15 +0300 [thread overview]
Message-ID: <e96e9eeb0705222254j4380860ka5377fadd781b796@mail.gmail.com> (raw)
Hello.
I decided to dump version 2.25 as Marcel recommended and fight
my way with d-bus on my embedded.
So i'm going to try to build bluez-utils 3.10.1 on my platform.
I wanted to ask -
Are there more dependencies apart from d-bus (i saw HAL ?)?
Thank You
H.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2007-05-23 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 5:54 Voni Hakau [this message]
2007-05-23 7:21 ` [Bluez-users] bluez-utils dependencies 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=e96e9eeb0705222254j4380860ka5377fadd781b796@mail.gmail.com \
--to=hakauvoni@gmail.com \
--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