Subject: Re: [Bluez-devel] cross compiling bluez-utils
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
In-Reply-To: <848611830@web.de>
References: <848611830@web.de>
Content-Type: text/plain
Message-Id: <1107618796.6921.156.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Reply-To: bluez-devel@lists.sourceforge.net
Date: Sat, 05 Feb 2005 16:53:16 +0100

Hi Martin,

> > I crosscompiled bluez-libs, bluez-utils and even hciemu for ARM platform 
> > and they work fine. I am preparing a little how-to for those insterested 
> > on doing the same thing.
> 
> They work perfectly here, too. Thanks for the hint! I just found it a little inconvenient to find the /etc/bluetooth/ directory in my ARM gcc directory. To be more specific:
> 
> The compiler, libs, include, ... directories reside under /usr/arm/arm-linux. That is set with 'prefix'. The executables then go to something like /home/mm/arm/ramdisk/mnt by setting 'exec_prefix' accordingly. I thought it to be funny to see /etc/bluetooth/ in the ramdisk rather than in the compiler area.

are you sure that exec_prefix is meant for cross-compiling. From my
knowledge it is for architecture dependent executables that will reside
in the same filesystem. For example for NFS exports.

Regards

Marcel


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel