Linux bluetooth development
 help / color / mirror / Atom feed
From: "Tushar Paturde" <tusharpaturde@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Doubts related to BlueZ and JSR-82
Date: Wed, 11 Apr 2007 09:52:31 +0530	[thread overview]
Message-ID: <b621074b0704102122t9a942c6v7ee44d03ea342d33@mail.gmail.com> (raw)
In-Reply-To: <2bf8a3380704101510q7bdbe0ep7fd39473a5dae73@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1849 bytes --]

Hi Bruno,
Bluez library give you access to your bluetooth hardware . So if your bluez
library calls are working and ur jsr82 implementation is using Bluez library
functions it should work for u.
As I understand Impronto, Avetana gives complete solution for JSR82
including native library.
Impronto internally uses Bluez library only.


regards,
Tushar

On 4/11/07, Bruno Cavaler Ghisi <brunogh@gmail.com> wrote:
>
> Just explaining better... will I need any other lib in the application
> classpath to work?
>
> Thanks,
>
> 2007/4/9, Bruno Cavaler Ghisi <brunogh@gmail.com>:
> > Hi,
> >
> > I am developing some stuff using jsr-82 and I would like to try it in
> > a jse application under Linux.
> >
> > I read about the BlueZ protocol stack and I have installed its
> > packages, however I do not know if I just need to have it in order to
> > the app work, because I read about other things like Impronto, Avetana
> > and I got confused... All of these are bluetooth protocol stacks? Will
> > I need anything else to run my application? Does anybody has any good
> > link about it?
> >
> > Thanks in advance.
> > Bruno
> >
>
>
> --
> Bruno Cavaler Ghisi
> Graduando de Sistemas de Informação
> Universidade Federal de Santa Catarina
>
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>



-- 
Tushar Paturde

[-- Attachment #1.2: Type: text/html, Size: 2498 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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-04-11  4:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 17:01 [Bluez-users] Doubts related to BlueZ and JSR-82 Bruno Cavaler Ghisi
2007-04-10 22:10 ` Bruno Cavaler Ghisi
2007-04-11  4:22   ` Tushar Paturde [this message]
2007-04-12 18:24     ` Bruno Cavaler Ghisi
2007-04-13  5:43       ` Mahtab Hossain

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=b621074b0704102122t9a942c6v7ee44d03ea342d33@mail.gmail.com \
    --to=tusharpaturde@gmail.com \
    --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