From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [gbluezconf] D-Bus client prototype
Date: Thu, 26 Jan 2006 22:09:24 +0100 [thread overview]
Message-ID: <1138309764.5901.153.camel@localhost> (raw)
In-Reply-To: <e1effdeb0601261259h7eb14f95wc315f53a2c0baa14@mail.gmail.com>
Hi Claudio,
> A new prototype version is available at:
> http://www.cin.ufpe.br/~ckt/gbluezconf/gbluezconf-00.04.tar.gz
you still depend on a "bluetooth/dbus.h" file that is not part of BlueZ
yet. Why don't you include a copy of it?
The error looks like this:
pair.c:41:28: error: bluetooth/dbus.h: No such file or directory
pair.c: In function '_dbus_pair_hci_signal_filter_cb':
pair.c:516: error: 'DEV_HCI_INTERFACE' undeclared (first use in this function)
pair.c:516: error: (Each undeclared identifier is reported only once
pair.c:516: error: for each function it appears in.)
...
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-01-26 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 22:27 [Bluez-devel] [gbluezconf] D-Bus client prototype Claudio Takahasi
2005-12-20 23:22 ` Marcel Holtmann
2005-12-21 18:51 ` Claudio Takahasi
2005-12-21 19:17 ` Marcel Holtmann
2006-01-26 20:59 ` Claudio Takahasi
2006-01-26 21:09 ` Marcel Holtmann [this message]
2006-01-26 21:44 ` Claudio Takahasi
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=1138309764.5901.153.camel@localhost \
--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;
as well as URLs for NNTP newsgroup(s).