From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluez build problem
Date: Fri, 13 Jun 2008 10:25:03 -0500 [thread overview]
Message-ID: <4852914F.6020209@earthlink.net> (raw)
In-Reply-To: <e96e9eeb0806130507u139f58a2sa7094a65f9ecff17@mail.gmail.com>
On 06/13/2008 07:07 AM, Voni Hakau wrote:
> Hi all,
>
> I'm cross compiling bluez-util to my platform, so I use something like
> --prefix=/path/to/my/platform/root/filesystem/usr. Everything builds
> and installs perfectly.
>
> But, in my platform, bluez now thinks that all the files are located
> in the path /path/to/my/platform/root/filesystem/usr (it is hard coded
> in the binaries), which doesn't really exists on the platform - it was
> just on my host, where I built my root fs for the platform. I need to
> install everything on my host to that path, but on the platform I need
> bluez to ignore it...
>
> Any suggestions ? I can always use --prefix=/usr and then manually
> copy all the files to /path/to/my/platform/root/filesystem/usr but
> that is too hard... there must be a better way..
>
> Thank you!
> Voni
>
Hi Voni.
Try to create a package instead. Use --prefix=/usr when you configure,
but use DESTDIR=/tmp/buildplace when you install.
That should install the files to /tmp/buildplace. Use tar(1) to create a
tarball of the files in /tmp/buildplace, or even better, use a packager
for your preferred platform.
During configuration, your command line might look like this:
make --prefix=/usr
When you "install" the package, you'll use this command:
make install DESTDIR=/tmp/buildplace
Obviously, the files won't be installed to the right place. No problem,
use tar(1).
cd /tmp/buildplace
tar czf /tmp/bluez-x.xx-i386.tar.gz *
Now you have a tarball that you can install wherever you wish, including
the correct place for your platform,
/path/to/my/platform/root/filesystem/usr.
Good luck.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-06-13 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 12:07 [Bluez-users] Bluez build problem Voni Hakau
2008-06-13 15:25 ` Mumia W.. [this message]
2008-06-16 12:05 ` Voni Hakau
2008-06-16 22:41 ` Mumia W..
2008-06-30 12:06 ` Voni Hakau
2008-06-30 12:09 ` Voni Hakau
2008-07-01 15:09 ` jayjwa
2008-07-02 7:56 ` Voni Hakau
2008-07-03 22:18 ` jayjwa
2008-06-18 7:20 ` [Bluez-users] Error encounter when connecting A2DP following wiki instruction ! How to connect A2DP ? colorant
2008-06-19 8:20 ` [Bluez-users] When Connect A2DP : Error 22 while configuring device colorant
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=4852914F.6020209@earthlink.net \
--to=paduille.4061.mumia.w+nospam@earthlink.net \
--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.