All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mats Erik Andersson <mats.andersson64@comhem.se>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] configure: error: Bluetooth library is required
Date: Mon, 09 Jul 2007 14:15:26 +0200	[thread overview]
Message-ID: <1183983327.5105.27.camel@localhost> (raw)
In-Reply-To: <BAY102-W16AA72BD57037F1749B764F0060@phx.gbl>

Dear Robert,

m=E5n 2007-07-09 klockan 11:40 +0000 skrev Robert Rawlins:
> Morning Mats,
>  =

> Thanks for your reply. I haven't copied my header files across, i'm
> not even sure how too :-D
>  =

> Can you explain the installation process for me? at the moment I'm
> doing it as follows.
>  =

> 1) Download libs and utils files from bluez.org
> 2) Untar those files using tar xzf filename.tar.gz
> 3) cd to the directory for libs
> 4) ./configure, make, make install
> 5) cd to the utils directory
> 6) ./configure --with-bluez=3D/usr/local/lib
>  =

> And that's when i get my error, by the sounds of what you have been
> saying i must be missing something out but i have no idea what. I
> don't do much compiling from source so this is all quite new to me.
>  =

> Thanks again for your help, it really is appreciated.
>  =

> Rob
> =


The quickest way is to create a directory =


# mkdir -p /usr/local/include/bluetooth/

and then copy the header files by hand =


# cp /path/to/source/for/bluez-libs-3.12/include/*.h \
            /usr/local/include/bluetooth/

The lacking of those header files, i.e. detailed descriptions of
bluez-utils-3.12, is probably the reason why you could not build
bluez-utils, even though the static and shared libraries were
present. I am somewhat puzzeled that "make install" did not put
the headers in the correct place, but give the above manipulation
a chance, and we will figure out the rest when there is no hurry.

By the way, your very first effort with BLUEZ_LIBS essentially
only lacked a second necessary variable:

   BLUEZ_LDFLAGS=3D"-I/usr/local/include"
   BLUEZ_LIBS=3D"-L/usr/local/lib -lbluetooth"

but it is safer to use "--with-bluez=3D/usr/local"

Good luck this time!

Best regards,	Mats E A

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-07-09 12:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 11:40 [Bluez-users] configure: error: Bluetooth library is required Robert Rawlins
2007-07-09 12:15 ` Mats Erik Andersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-09 14:16 Robert Rawlins
2007-07-09 12:34 Robert Rawlins
2007-07-09 13:54 ` Mats Erik Andersson
2007-07-09 11:43 Robert Rawlins
2007-07-08 16:52 Robert Rawlins
2007-07-09 11:02 ` Mats Erik Andersson
2007-07-06 16:57 Robert Rawlins
2007-07-06 21:45 ` Manuel Naranjo
2007-07-06 22:00 ` Mats Erik Andersson
2007-07-07  9:32 ` Mats Erik Andersson
2007-07-06 16:28 Robert Rawlins
2007-07-05 13:53 Robert Rawlins
2007-07-05 14:13 ` Manuel Naranjo

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=1183983327.5105.27.camel@localhost \
    --to=mats.andersson64@comhem.se \
    --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.