From: Robert Wlaschin <robertw@healthhero.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] cross-compiling bluez-utils.3.1
Date: Wed, 28 Jun 2006 17:07:12 +0000 (UTC) [thread overview]
Message-ID: <loom.20060628T185219-52@post.gmane.org> (raw)
In-Reply-To: 6297d67c0606272053xff3b84dwf59410cce7bc658b@mail.gmail.com
Mayank Batra <mayankbatra <at> gmail.com> writes:
>
>
> Hi Robert,
> On 6/28/06, Robert Wlaschin <robertw <at> healthhero.com> wrote:
> I seem to be having problems with the latest version of bluez-utils. It
> seemsthat dbus is a required component of the
> 3.1 release; which isn't cross-compilefriendly (the dbus build complains about
> cross-compiling) -- a previous versionof bluez-utils (2.21) is. In the 2.21
> release there was an option to compilewithout dbus, is there a work around for
> the 3.1/if so, how? If not, anysuggestions about cross-compiling the stock
> bluez-utils.3.1 (including dbus asnecessary) for an ARM processor?Robert
>
> Actually the latest bluez-utils are not even compiling on PC. It complains
> that dbus package is not present.
>
> Regards,
> Mayank
>
>
>
> 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 <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
Mayank,
Thanks for the response. There are some posts in the forum about problems with
cross-compiling.
To get past the dbus problem, if you don't already have the dbus source you'll
need to get it from http://www.freedesktop.org/wiki/Software/dbus, after that
you'll need to get a new version of bluez-utils-3.1/acinclude.m4 from the bluez
CVS -- there is a bug in this file that looks for the incorrect dbus libs.
After you have updated that file follow the instructions in INSTALL for
rebuilding the configuration script.
As a side note you may need to add PKG_CONFIG_PATH=$(BLUEZ_LIBS_BUILD_DIR) to
your command-line when running ./configuration (BLUEZ_LIBS_BUILD_DIR is a make
variable that needs to point to your bluez-libs-3.1 directory).
Please search the group for more information concerning this issue. I hope this
helps.
Robert
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 17:07 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 [this message]
2006-06-29 6:57 ` Mayank Batra
2006-06-28 7:28 ` Marcel Holtmann
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=loom.20060628T185219-52@post.gmane.org \
--to=robertw@healthhero.com \
--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).