From: Marcel Holtmann <marcel@holtmann.org>
To: R.Schade@tu-braunschweig.de
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] missing include-files with debian
Date: Wed, 08 Sep 2004 11:39:37 +0200 [thread overview]
Message-ID: <1094636377.5384.14.camel@notepaq> (raw)
In-Reply-To: <517CF7F08A05D4118C380000E869BFA4BDED83@emg_ntserv2>
Hi Ralf,
> I had installed Debian-stable (2.4.20) with the bluez-debian-packages (I did
> not compile the bluez-sources myself). My USB-bluetooth-dongle works fine.
> Now, I want code some little application. So I have include the
> bluetooth-headerfiles:
>
> #include <bluetooth/bluetooth.h>
> #include <bluetooth/rfcomm.h>
> #include <bluetooth/hci.h>
> #include <bluetooth/hci_lib.h>
>
> The standard include-directory is /usr/include. Directory "bluetooth" exists
> there, but contains only one headerfile (bnep.h). Why are missing the other
> bluez-headerfiles there?
> Is this a debian-"problem" with the package and I have to install/copy/link
> the files manually? I had found the missing files at the kernel-sources and
> at the bluez-sources.
install the libbluetooth-dev package, but these Debian Woody packages
are very old. Maybe you wanna at least update to Sarge.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-09-08 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 8:20 [Bluez-users] missing include-files with debian R.Schade
2004-09-08 9:39 ` Marcel Holtmann [this message]
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=1094636377.5384.14.camel@notepaq \
--to=marcel@holtmann.org \
--cc=R.Schade@tu-braunschweig.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox