From: Aras Vaichas <arasv@magtech.com.au>
To: Bluez Users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Bluez + dbus for ARM solutions?
Date: Thu, 01 May 2008 16:45:29 +1000 [thread overview]
Message-ID: <48196709.9030104@magtech.com.au> (raw)
Hi,
can someone point me to where I can find scripts/patches that will help
me build ARM cross-compiled versions of Bluez + dbus for ARM?
Is there a well know set of dbus+bluez versions that are known to work
for cross-compiling, or does everyone just hack the configure files
until it works?
I'm currently stuck in dependency hell trying to get dbus to
cross-compile. So far I've got expat, bluez-libs, and libusb compiled.
I saw that someone recommended Scratchbox (for dbus) but I'd rather not
do that because I am able to cross-compile every single other library
and application for my distribution (including Python) without requiring
a method like Scratchbox.
Aras Vaichas
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2008-05-01 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 6:45 Aras Vaichas [this message]
2008-05-01 9:56 ` [Bluez-users] Bluez + dbus for ARM solutions? Jelle de Jong
2008-05-02 0:47 ` Aras Vaichas
2008-05-02 8:12 ` Jelle de Jong
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=48196709.9030104@magtech.com.au \
--to=arasv@magtech.com.au \
--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;
as well as URLs for NNTP newsgroup(s).