From: mulata@gmx.de
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Using bluez-utils from another application
Date: Thu, 15 May 2008 16:59:33 +0200 [thread overview]
Message-ID: <20080515145933.161540@gmx.net> (raw)
In-Reply-To: <1210844175.7025.29.camel@violet.holtmann.net>
Hi Marcel,
thanks for your hint.
I've tried to compile some of the recent Versions of dbus again. But it alw=
ays fails with:
if arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include -DDBUS_L=
OCALEDIR=3D\"/opt/devel/toolchains/arm9/arm-linux/share/locale\" -DDBUS_COM=
PILATION -DDBUS_DAEMONDIR=3D\"/opt/devel/toolchains/arm9/arm-linux/bin\" -D=
DBUS_MACHINE_UUID_FILE=3D\""/opt/devel/toolchains/arm9/arm-linux/var/lib/db=
us/machine-id"\" -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations -=
Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-e=
qual -Wsign-compare -fno-common -fPIC -MT dbus-launch.o -MD -MP -MF ".deps/=
dbus-launch.Tpo" -c -o dbus-launch.o dbus-launch.c; \
then mv -f ".deps/dbus-launch.Tpo" ".deps/dbus-launch.Po"; else rm =
-f ".deps/dbus-launch.Tpo"; exit 1; fi
dbus-launch.c: In Funktion =BBkill_bus_when_session_ends=AB:
dbus-launch.c:413: error: impossible constraint in `asm'
dbus-launch.c:414: error: impossible constraint in `asm'
dbus-launch.c:445: error: impossible constraint in `asm'
dbus-launch.c:444: error: impossible constraint in `asm'
dbus-launch.c:451: error: impossible constraint in `asm'
dbus-launch.c:475: error: impossible constraint in `asm'
Anyway this is not your problem, but any help is welcome.
Maybee my header files are too old since im using as cross compiler arm-lin=
ux-gcc 3.3.3.
Maybee I can compile an older version of dbus.
However, which dbus version needs bluez-utils at least?
Thanks
Johannes
-------- Original-Nachricht --------
> Datum: Thu, 15 May 2008 11:36:15 +0200
> Von: Marcel Holtmann <marcel@holtmann.org>
> An: BlueZ users <bluez-users@lists.sourceforge.net>
> Betreff: Re: [Bluez-users] Using bluez-utils from another application
> Hi Johannes,
> =
> > Just installed bluez-libs-2.25 and bluez-utils-2.25.
> > I know there are more recent versions avaiable but since Im developping
> for an Embedded Linux System based on ARM9 my resources are very limited
> and I was not able to compile "libdbus" which is necessary for the recent
> version of bluez.However... the installed versions are working fine. =
> =
> your version is ancient. I have the release date as January 2006 and
> this means it is over two years old. That is a full lifetime in the
> Linux world.
> =
> I am simply not buying the D-Bus cross-compilation issue. Sorry, but it
> is not that hard.
> =
> > By the way Im using a 2.2.21 Kernel, but the bluetooth related stuff is
> patched to 2.2.26.
> =
> We never had a 2.2.21 kernel with Bluetooth support.
> =
> > My goal is to use functionalities provided by hciconfig and hcitool in
> another C Program. Finally this features (e.g. Listing active local
> bluetooth devices, do a scan for remote devices, ask for available servic=
es) will
> be visualized graphically in this C programm.
> =
> You are going to duplicate all the work that has been done for now
> reason. Spending the time to cross-compile D-Bus would be better
> invested.
> =
> > So there are basically tow ways:
> > - System Calls like system("hciconfig") (which is not very handy and
> beautiful)
> > - Using the Library
> =
> Again, cross-compile D-Bus and use our D-Bus based API. It is more
> elegant than any low-level stuff will ever be.
> =
> > Concerning the second point (using Library) I did some research in
> hciconfig.c.
> > I expected that there a some higher-level functions that I can call from
> another C programm by including the necessary header files.
> > But it seems there must be also done some low-level stuff, like opening
> a HCI socket.
> =
> Yes. You always have to open a HCI raw socket to do raw packet
> manipulation.
> =
> 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-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-- =
Martin Kupf
249 Spiele f=FCr nur 1 Preis. Die GMX Spieleflatrate schon ab 9,90 Euro.
Neu: Asterix bei den Olympischen Spielen: http://flat.games.gmx.de
-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-05-15 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 11:24 [Bluez-users] Using bluez-utils from another application mulata
2008-05-15 9:36 ` Marcel Holtmann
2008-05-15 9:52 ` [Bluez-users] i would like to donate a bunch of non working bluetooth hardware Jelle de Jong
2008-05-15 14:59 ` mulata [this message]
2008-05-15 15:02 ` [Bluez-users] Using bluez-utils from another application 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=20080515145933.161540@gmx.net \
--to=mulata@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.