From: "Voni Hakau" <hakauvoni@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] easiest way to get OBEX support (client/server) ?
Date: Sat, 30 Aug 2008 10:16:09 +0300 [thread overview]
Message-ID: <e96e9eeb0808300016l7b0118cbj13c8e410cd8dcb95@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0808290445110.26779@nge2.ngu.pk>
On Fri, Aug 29, 2008 at 3:13 PM, jayjwa <jayjwa@atr2.ath.cx> wrote:
> I've tried obex-data-server and obexd, but I couldn't get either one working.
> I asked on the list but there wasn't a reply. The one I use currently is one I
Also there is an 'obex' project in the bluez cvs, i think it is obex
client, but i can't use it because it requires libxml and we use
libexpat in our embedded system (libxml is bloated!)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-08-30 7:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 10:49 [Bluez-users] easiest way to get OBEX support (client/server) ? Voni Hakau
2008-08-25 10:56 ` Voni Hakau
2008-08-29 12:13 ` jayjwa
2008-08-30 7:11 ` Voni Hakau
2008-08-30 9:34 ` Marcel Holtmann
2008-08-30 8:44 ` Voni Hakau
2008-08-30 10:50 ` Marcel Holtmann
2008-08-30 7:16 ` Voni Hakau [this message]
2008-08-30 9:30 ` 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=e96e9eeb0808300016l7b0118cbj13c8e410cd8dcb95@mail.gmail.com \
--to=hakauvoni@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