[Bluez-users] cross-compilation miniHowto, first change

[Marco Trudel <mtrudel@gmx.ch>]

[-- Attachment #1: Type: text/plain, Size: 4802 bytes --]

Hello everybody

I just noticed that with
LDFLAGS=-L/foobar/bluez/lib, the lib path can be specified...

So, you can ignore my last email and read this mini-howto if you're interested.

kind regards
Marco


Marco Trudel wrote:
> Hello Marcel
> 
> Is this ok?
> Any improvement suggestions? Anyone?
> 
> 
> kind regards
> Marco
> 
> 
> Marcel Holtmann wrote:
> 
>> Hi,
>>
>>
>>> Thanks Erwin. I also used --libdir=  too and I can compile the utils. 
>>> (Haven't tested them yet - trying to get the kernel up and running).
>>>
>>> I wasn't sure about using --host as the script gave some kind of 
>>> error about not using it.
>>
>>
>>
>> may someone write a small BlueZ cross-compilation howto that I can add
>> to the website?
>>
>> 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-users mailing list
>> Bluez-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bluez-users
>>
>>
> 
> ------------------------------------------------------------------------
> 
> This document shows how to cross-compile bluez for an arm-processor on an i686 processor.
> It can be used as starting point if you have to cross-compile bluez yourself.
> 
> date/version: 01 Feb. 2005, v0.1
> author:       Marco Trudel <mtrudel@gmx.ch>
> 
> If you need help, please use the bluez-user list.
> 
> ------------------------------------------------------------
> 
> This document assumes you have the toolchain installed in /usr/local/arm.
> Version 2.95.3 is used in this description.
> That means a directory called "/usr/local/arm/2.95.3/arm-linux" exists.
> Bluez will be installed into /opt/bluez (feel free to choose another location).
> 
> Ensure that the crosscompile binaries are in $PATH.
> For example, do: export PATH="$PATH:/usr/local/arm/2.95.3/bin"
> 
> ########## 1. compile bluez-libs ##########
> - extract bluez-libs and change into the directory
> - configure the makefiles for cross-compiling. run:
>         ./configure --build=i686-pc-linux-gnu    \
>                     --host=arm-linux             \
>                     --sysconfdir=/opt/bluez/etc  \
>                     --prefix=/opt/bluez
> 
> - Check the output. Some interesting lines:
>         checking for arm-linux-gcc... arm-linux-gcc
>         checking whether the C compiler works... yes
>         checking whether we are cross compiling... yes
> - run "make", "make install"
> 
> The bluez libs are now intalled in /opt/bluez.
> At this point, compiling the bluez-utils still fails because it doesn't
> find the library (--with-bluez=/opt/bluez dosn't work for me, the error is:
> /usr/local/arm/2.95.3/arm-linux/bin/ld: cannot find -lbluetooth)
> To make it work, we install the bluez-libs in the arm-linux directory.
> To keep that directory clean, we'll remove bluez from it later again.
> If someone knows why --with-bluez doesn't work, please inform me.
> 
> Run:
>         ./configure --build=i686-pc-linux-gnu    \
>                     --host=arm-linux             \
>                     --sysconfdir=/opt/bluez/etc  \
>                     --prefix=/usr/local/arm/2.95.3/arm-linux
>         make install # do not run "make"
> 
> 
> ########## 2. compile bluez-utils ##########
> - extract bluez-utils and change into the directory
> - configure the makefiles for cross-compiling. run:
>         ./configure --build=i686-pc-linux-gnu   \
>                     --host=arm-linux            \
>                     --sysconfdir=/opt/bluez/etc \
>                     --prefix=/opt/bluez
> - run "make" and "make install"
> 
> 
> ########## 3. clean up ##########
> As promised in the first step, we keep our arm-linux directory clean.
> So change back into the bluez-libs folder and run:
> make uninstall
> 
> 
> ######### 4. final steps, tests ##########
> Please note: This mini-howto assumes you have a bluetooth enabled kernel.
> If you haven't already, install it now.
> 
> Depending on your setup, you might be interested in every kb
> of diskspace to save. With -s stripping and removing of unnecessary
> files, it's possible to save ~350kb...
> 
> - copy /opt/bluez to your target platform.
> - add "/opt/bluez/lib" to /etc/ld.so.conf and, run "ldconfig"
> - run "./hcid -n" in /opt/bluez/sbin
> Check the output.
> If everything works well, abort hcid and start it withhout "-n".
> 
> - "/opt/bluez/bin/hcitool dev" should show you your devices
> - "/opt/bluez/bin/hcitool scan" perform an inquiry scan

[-- Attachment #2: bluezCrossCompiling-miniHowto --]
[-- Type: text/plain, Size: 2648 bytes --]

This document shows how to cross-compile bluez for an arm-processor on an i686 processor.
It can be used as starting point if you have to cross-compile bluez yourself.

date/version: 01 Feb. 2005, v0.1.1
author:       Marco Trudel <mtrudel@gmx.ch>

If you need help, please use the bluez-user list.

------------------------------------------------------------

This document assumes you have the toolchain installed in /usr/local/arm.
Version 2.95.3 is used in this description.
That means a directory called "/usr/local/arm/2.95.3/arm-linux" exists.
Bluez will be installed into /opt/bluez (feel free to choose another location).

Ensure that the crosscompile binaries are in $PATH.
For example, do: export PATH="$PATH:/usr/local/arm/2.95.3/bin"

########## 1. compile bluez-libs ##########
- extract bluez-libs and change into the directory
- configure the makefiles for cross-compiling. run:
        ./configure --build=i686-pc-linux-gnu    \
                    --host=arm-linux             \
                    --sysconfdir=/opt/bluez/etc  \
                    --prefix=/opt/bluez

- Check the output. Some interesting lines:
        checking for arm-linux-gcc... arm-linux-gcc
        checking whether the C compiler works... yes
        checking whether we are cross compiling... yes

- Explanation of the switches:
        --build        the build platform
	--host         the target platform
	--sysconfdir   where bluez will expect etc (feel free to use /etc)
	--prefix       where bluez will be installed to

- run "make", "make install"

########## 2. compile bluez-utils ##########
- extract bluez-utils and change into the directory
- configure the makefiles for cross-compiling. run:
        ./configure --build=i686-pc-linux-gnu   \
                    --host=arm-linux            \
                    --sysconfdir=/opt/bluez/etc \
                    --prefix=/opt/bluez         \
                    LDFLAGS=-L/opt/bluez/lib
- run "make" and "make install"


######### 3. final steps, tests ##########
Please note: This mini-howto assumes you have a bluetooth enabled kernel.
If you haven't already, install it now.

Depending on your setup, you might be interested in every kb
of diskspace to save. With -s stripping and removing of unnecessary
files, it's possible to save ~350kb...

- copy /opt/bluez to your target platform.
- add "/opt/bluez/lib" to /etc/ld.so.conf and, run "ldconfig"
- run "./hcid -n" in /opt/bluez/sbin
Check the output.
If everything works well, abort hcid and start it withhout "-n".

- "/opt/bluez/bin/hcitool dev" should show you your devices
- "/opt/bluez/bin/hcitool scan" perform an inquiry scan