Re: [Bluez-devel] Cross Compile Blues ....

[Marcel Holtmann <marcel@holtmann.org>]

Hi Peter,

> thank you. This helped to build the libraries correctly. Library build now
> looks like this (if anybody runs into the same problem):
> 
> # configure and make bluez libs
> pushd bluez/bluez-libs-2.11
> ./configure --host=$TARGET --build=i686-pc-linux-gnu \
>             --with-kernel=$LINUX_DIR \
>             --libdir=/lib --includedir=$XPREFIX/include
> make
> make install DESTDIR=$XPREFIX
> popd

for what do you still need the --includedir ?

> However, it fails with utils. But this isn't much of a problem, for
> now I can live with the hack below....
> 
> When I don't use prefix with utils I get some real strange problem with
> the include pathes. Looks like the native include pathes are used ?!?
> 
> # configure and make bluez utils
> pushd bluez/bluez-utils-2.11
> ./configure --prefix=$XPREFIX --host=$TARGET --build=i686-pc-linux-gnu \
>             --with-kernel=$LINUX_DIR \
>             --libdir=$XPREFIX/lib --includedir=$XPREFIX/include
> #            --sysconfdir=/etc
> #            --without-glib
> # can't figure out how to get this right .......... so...
> echo "#undef CONFIGDIR" >> config.h
> echo "#define CONFIGDIR \"/etc/bluetooth\"" >> config.h
> make
> make install
> popd

Sounds like a bug to me. However I don't finally understand why you
wanna install everything into under / .

I never did any cross-compiling so far, but I am open for every
enhancement to make it easier.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel