From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] cross-compiling bluez-utils.3.1
Date: Wed, 28 Jun 2006 09:28:18 +0200 [thread overview]
Message-ID: <1151479698.9544.1.camel@localhost> (raw)
In-Reply-To: <loom.20060628T033626-329@post.gmane.org>
Hi Robert,
> I seem to be having problems with the latest version of bluez-utils. It seems
> that dbus is a required component of the 3.1 release; which isn't cross-compile
> friendly (the dbus build complains about cross-compiling) -- a previous version
> of bluez-utils (2.21) is. In the 2.21 release there was an option to compile
> without dbus, is there a work around for the 3.1/if so, how? If not, any
> suggestions about cross-compiling the stock bluez-utils.3.1 (including dbus as
> necessary) for an ARM processor?
the D-Bus library is mandatory now. Hence the new major version number.
Regards
Marcel
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&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-06-28 7:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 1:36 [Bluez-devel] cross-compiling bluez-utils.3.1 Robert Wlaschin
2006-06-28 3:53 ` Mayank Batra
2006-06-28 17:07 ` Robert Wlaschin
2006-06-29 6:57 ` Mayank Batra
2006-06-28 7:28 ` Marcel Holtmann [this message]
2006-06-28 17:11 ` Steve Finney
2006-06-28 17:33 ` Marcel Holtmann
2006-07-19 4:09 ` ifq
2006-07-19 7:05 ` Rahul Tank
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=1151479698.9544.1.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).