From: "rohit puri" <rohitpuri.rohit@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] DBus error <dbus/dbus-arch-deps.h> is missing
Date: Fri, 5 Oct 2007 19:10:32 +0530 [thread overview]
Message-ID: <d5d240eb0710050640p1d9454f3peb935cbcbb6052bf@mail.gmail.com> (raw)
In-Reply-To: <1191589377.10698.168.camel@violet>
[-- Attachment #1.1: Type: text/plain, Size: 1874 bytes --]
Hi Marcel,
Thanks very much for your assistance but still some errors are there
even I have changed the include path to -1
'DBusConnection' undeclared (first use in this function)
dbus2.c:10: error: (Each undeclared identifier is reported only once
dbus2.c:10: error: for each function it appears in.)
dbus2.c:10: error: 'connection' undeclared (first use in this function)
dbus2.c:12: error: 'DBusMessage' undeclared (first use in this function)
dbus2.c:12: error: 'message' undeclared (first use in this function)
dbus2.c:12: error: 'reply' undeclared (first use in this function)
dbus2.c:16: error: 'DBUS_BUS_SYSTEM' undeclared (first use in this function)
dbus2.c:22: error: 'DBUS_TYPE_STRING' undeclared (first use in this
function)
dbus2.c:22: error: 'DBUS_TYPE_INVALID' undeclared (first use in this
function)
Regards,
Rohit
On 10/5/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Rohit,
>
> > whenever I am compiling my program of
> > dbus for interprocess communication .i am getting following error .I
> > have downloaded a latest version of dbus 1.1.2
> >
> >
> > Here I am writing the program and all the errors I am facing
> > #include <stdio.h>
> > #include <stdlib.h>
> > #include <dbus-1.0/dbus/dbus.h>
>
> you includes are not complete. You can't use the "dbus-1.0" prefix, you
> have to change the include path (-I).
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
[-- Attachment #1.2: Type: text/html, Size: 2519 bytes --]
[-- Attachment #2: Type: text/plain, Size: 314 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-10-05 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 12:52 [Bluez-users] DBus error <dbus/dbus-arch-deps.h> is missing rohit puri
2007-10-05 13:02 ` Marcel Holtmann
2007-10-05 13:40 ` rohit puri [this message]
2007-10-06 9:24 ` 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=d5d240eb0710050640p1d9454f3peb935cbcbb6052bf@mail.gmail.com \
--to=rohitpuri.rohit@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