From: "Rupinder Singh" <plitanium@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Introduction
Date: Sat, 20 Dec 2008 00:38:14 +0530 [thread overview]
Message-ID: <c3cfaf5e0812191108m4bdaa41bw1f2acdbef9b3bbb3@mail.gmail.com> (raw)
In-Reply-To: <1229712698.879.4.camel@californication>
[-- Attachment #1.1: Type: text/plain, Size: 851 bytes --]
Hi,
I wanted to learn about the pre-requisites of getting into the development
part. I guess it would be better If I go through the source code again...
Thanks,
Rupinder
On Sat, Dec 20, 2008 at 12:21 AM, Marcel Holtmann <marcel@holtmann.org>wrote:
> Hi Rupinder,
>
> > I have a good experience of g++ and have worked with bluetooth
> > protocols using J2ME. Kindly guide me as to where do I begin before
> > getting into blueZ development.
>
> I have no idea what you are expecting from us here. We are not using C++
> or J2ME for that matter for BlueZ at all.
>
> Regards
>
> Marcel
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
[-- Attachment #1.2: Type: text/html, Size: 1363 bytes --]
[-- Attachment #2: Type: text/plain, Size: 79 bytes --]
------------------------------------------------------------------------------
[-- 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:[~2008-12-19 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 16:46 [Bluez-devel] Introduction Rupinder Singh
2008-12-19 18:51 ` Marcel Holtmann
2008-12-19 19:08 ` Rupinder Singh [this message]
2008-12-23 23:18 ` Marcel Holtmann
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=c3cfaf5e0812191108m4bdaa41bw1f2acdbef9b3bbb3@mail.gmail.com \
--to=plitanium@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