From: "Vikas Sinha" <compuvikas@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] missing bluetooth header file
Date: Fri, 2 Mar 2007 10:50:37 +0530 [thread overview]
Message-ID: <1ab01fb50703012120q62e91355rcad41055dd7d59a0@mail.gmail.com> (raw)
In-Reply-To: <ddea76ce0703010726j32cf3736kf8f5391c4c492183@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 4024 bytes --]
Hi Meenakshi,
u need to compile bluez-devel. Download sorce then untar it into
/usr/local/src (you can put it to anywhere. I generally put it there). go
into that folder and do
./configure
make
make install
it will compile and put header files to its location. i.e.
/usr/include/bluetooth or /usr/local/include/bluetooth . if it create it in
second then simply copy it to first path. Then try to compile ur code. plz
check ur d-bus version also.
On 3/1/07, Meenakshi Seeballack <meena2010@gmail.com> wrote:
>
> In /usr/lib I have these files:
> /usr/lib/libbluetooth.so.2 rw- r - r
> /usr/lib/libbluetooth.so.2.4.1 rw- r - r
>
> And the header files are absent in /usr/include.
>
> The only header files I can see for bluetooth are here
> /usr/src/kernels/2.6.19-1.2911.fc6-i686/include/net/bluetooth/bluetooth.h
> /usr/src/kernels/2.6.19- 1.2911.fc6-i686/include/net/bluetooth/hci.h
> /usr/src/kernels/2.6.19-1.2911.fc6-i686/include/net/bluetooth/hci_core.h
> /usr/src/kernels/2.6.19-1.2911.fc6-i686/include/net/bluetooth/l2cap.h
> /usr/src/kernels/2.6.19- 1.2911.fc6-i686 /include/net/bluetooth/rfcomm.h
> /usr/src/kernels/2.6.19-1.2911.fc6-i686/include/net/bluetooth/sco.h
>
> >
> And the header files are absent in /usr/include. So how do I get the
> bluetooth folder with the header files in /usr/include?
> Where is the hci_lib.h header file?
>
> ----------------------------------------------------------------------------------
>
> On 01/03/07, bluez-devel-request@lists.sourceforge.net <bluez-devel-request@lists.sourceforge.net>
> wrote:
> >
> > Send Bluez-devel mailing list submissions to
> > bluez-devel@lists.sourceforge.net
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://lists.sourceforge.net/lists/listinfo/bluez-devel
> > or, via email, send a message with subject or body 'help' to
> > bluez-devel-request@lists.sourceforge.net
> >
> > You can reach the person managing the list at
> > bluez-devel-owner@lists.sourceforge.net
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Bluez-devel digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: missing bluetooth header file (Vikas Sinha)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Thu, 1 Mar 2007 20:36:08 +0530
> > From: "Vikas Sinha" <compuvikas@gmail.com >
> > Subject: Re: [Bluez-devel] missing bluetooth header file
> > To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
> > Message-ID:
> > < 1ab01fb50703010706j27966cf8j598eae2d38c9b28c@mail.gmail.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > ok plz check library path. did u have
> >
> > -rw-r--r-- 1 root root 52530 Aug 17 2004 libbluetooth.a
> > lrwxrwxrwx 1 root root 22 Jun 21 2006 libbluetooth.so ->
> > libbluetooth.so.1.0.10
> > lrwxrwxrwx 1 root root 22 May 4 2006 libbluetooth.so.1 ->
> > libbluetooth.so.1.0.10
> > -rwxr-xr-x 1 root root 49780 Aug 17 2004 libbluetooth.so.1.0.10
> >
> > these files in ur /usr/lib or in /usr/local/lib. if these files are
> > places
> > other place then u need to
> > export LD_LIBRARY_PATH=// lib path for these file. These files need at
> > the
> > time of compilation of any code containing bluetooth.h file. include
> > these
> > and i think ur programm will work
> >
> > Also check ur header files are present at /usr/include or not.
> >
> >
> > On 3/1/07, Meenakshi Seeballack < meena2010@gmail.com> wrote:
> > >
> > > the kernel is 2.6.19-1.2911.fc6-i686, and I assume bluez is installed
> > on
> > > the machine, since I tried "yum install bluez" and it says "nothing
> > to do"
> > >
> > -------------------------------------------------------------------------------------------------------
> > >
> > > On 01/03/07, bluez-devel-request@lists.sourceforge.net <
> > bluez-devel-request@lists.sourceforge.net>
> > > wrote:
> >
>
--
Impossible
itself contain
I M Possible
Vikas
[-- Attachment #1.2: Type: text/html, Size: 6922 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-03-02 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 15:26 [Bluez-devel] missing bluetooth header file Meenakshi Seeballack
2007-03-01 15:34 ` Tuomas Suutari
2007-03-02 5:20 ` Vikas Sinha [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-01 14:41 Meenakshi Seeballack
2007-03-01 15:06 ` Vikas Sinha
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=1ab01fb50703012120q62e91355rcad41055dd7d59a0@mail.gmail.com \
--to=compuvikas@gmail.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