From: Kartikey Parmar <kartikey2781@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: kartikey.parmar@matrixtelesol.com
Subject: Need help in Bluetooth programming with C
Date: Fri, 6 Feb 2009 18:01:31 +0530 [thread overview]
Message-ID: <6887eb5d0902060431t4a5d4d2bs929798ad8d664050@mail.gmail.com> (raw)
Hi there,
I m new to Bluetooth world of programming using BlueZ - the official
protocol stack for Linux.
I have install bluez-4.27 on Fedora core 9 in which I m finding .txt
file describing the APIs for C Programming but I don't find related
documentation of how to use the same to write our application using C
programming.
If I compile all .c files in the order in /src folder as described in
Makefile for "bluetoothd" sources, it gives no error. But the problem
in that is, I can't decide which function should I begin with to
initialize my Bluetooth dongle attached to USB port of the computer
and how to start inquiry, pairing & service discovery process using
those so called "Bluez D-Bus API".I m little confused about the use of
this bluez stack for my development in C programming.
Kindly guide me through how to solve this problem.
Pls reply at the earliest so I can continue my development.
Kartikey Parmar
reply other threads:[~2009-02-06 12:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6887eb5d0902060431t4a5d4d2bs929798ad8d664050@mail.gmail.com \
--to=kartikey2781@gmail.com \
--cc=kartikey.parmar@matrixtelesol.com \
--cc=linux-bluetooth@vger.kernel.org \
/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