From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Changing default paths in hcid?
Date: Fri, 09 Jun 2006 09:53:05 +0200 [thread overview]
Message-ID: <1149839585.6618.7.camel@localhost> (raw)
In-Reply-To: <CA21EAA4DF189C40A3BC30A5A75DA56002551241@ratatosk>
Hi Birger,
> I've cross compiled BlueZ libs and utils for an arm based platform and most things work nice. However, when running hcid it assumes to find things at a path that I defined as install path at the host system (i.e. set by the PREFIX flag).
>
> I did this since I do not want to install the cross compiled things on my host.
>
> I configured with:
> ./configure --prefix=[mypath] --host=arm-linux
>
> Does anyone know the correct way of cross compiling and install bluez on a target system I would appreciate some hints.
do the install with "make install DESTDIR=$PWD/tmp" and then pack up the
tmp/ directory.
Regards
Marcel
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-06-09 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 7:47 [Bluez-users] Changing default paths in hcid? Birger Kroon
2006-06-09 7:53 ` Marcel Holtmann [this message]
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=1149839585.6618.7.camel@localhost \
--to=marcel@holtmann.org \
--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.