Linux bluetooth development
 help / color / mirror / Atom feed
From: kwyjibo@ono.com
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Troubles cross-compiling utils... Resolved?
Date: Tue, 8 Mar 2005 02:08:38 +0100	[thread overview]
Message-ID: <4208B84C00014D22@resmta04.ono.com> (raw)

Hi, I found some troubles cross-compiling for Compulab ARM unit. First of=

all, I tried to do  it with gcc 3.3.2, but there were many problems, so I=

come back to 2.95.3, which it seems to be more kind...

First, I use this command, in addition with enviroment variables to tell
where the crosscompiling chain is located (v.g CC=3D/usr/local/arm/2.95.3=
/bin/arm-linux-gcc,
LD=3D/...)

./configure --prefix=3D/mnt/image --host=3Darm --with-bluez=3D/mnt/img/li=
b

The first problem I found is that it doesn't find the headers, but the co=
nfigure's
help doesn't say nothing about that... I tried,  like in other releases:

./configure --prefix=3D/mnt/image --host=3Darm --with-bluez=3D/mnt/img/li=
b --with-bluez-includes=3D/mnt/image/include

But throws the same error. I tried this, as I did before.

./configure --prefix=3D/mnt/image --host=3Darm --with-bluez-libs=3D/mnt/i=
mage/libs
--with-bluez-includes=3D/mnt/image/include

And now I passed the configure with no errors...

Next I tried to make, and compiling one of the tools it stopped:

/usr/local/arm/2.95.3/bin/arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I..    -=
I/mnt/image/include
 -I/mnt/image/include -Wall -O2 -c `test -f 'hcisecfilter.c' || echo './'=
`hcisecfilter.c
/usr/local/arm/2.95.3/bin/arm-linux-gcc -I/mnt/image/include  -I/mnt/imag=
e/include
-Wall -O2   -o hcisecfilter  hcisecfilter.o  -lbluetooth
/usr/local/arm/2.95.3/arm-linux/bin/ld: cannot find -lbluetooth

I notice that the tool app compiled before that was

/usr/local/arm/2.95.3/bin/arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I..    -=
I/mnt/image/include
 -I/mnt/image/include -Wall -O2 -c `test -f 'ppporc.c' || echo './'`pppor=
c.c
/usr/local/arm/2.95.3/bin/arm-linux-gcc -I/mnt/image/include  -I/mnt/imag=
e/include
-Wall -O2   -o ppporc  ppporc.o -L/mnt/image/lib -lbluetooth -lbluetooth

So I noticed that this one includes -L/mnt/image//lib, I edited the makef=
ile
of the tool directory, adding that directory to the tools who needed, and=

I managed to compile them...

I haven't tested yet, so I don't know if this is right, but may be it be
useful to someone.




-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2005-03-08  1:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08  1:08 kwyjibo [this message]
2005-03-08 12:19 ` [Bluez-devel] Troubles cross-compiling utils... Resolved? Anderson Rodrigues

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=4208B84C00014D22@resmta04.ono.com \
    --to=kwyjibo@ono.com \
    --cc=bluez-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox