From: Pierre-Yves Paulus <py@idlum.be>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CreateProxy usage?
Date: Wed, 02 Apr 2008 18:22:27 +0200 [thread overview]
Message-ID: <47F3B2C3.5050000@idlum.be> (raw)
In-Reply-To: <47F3B09F.5070709@aircable.net>
Hi Manuel,
> You don't need to link against bluez AFAIK, you only link against the
> sockets library which is included in libc. I'll try to write a wiki page
> today, the other day I had some troubles with my electric power
> provider, and forgot to make the wiki page.
That would be great! A I said, I've no idea about rfcomm sockets, so
example code would help me get up to speed.
> But I've been able to write 2 examples on as master, the other as slave
> using python and dbus, and I have C code around I can use too.
Very promising :-)
Best Regards,
Pierre-Yves
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-04-02 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 2:52 [Bluez-devel] CreateProxy usage? Manuel Naranjo
2008-03-31 3:20 ` Marcel Holtmann
2008-03-31 3:25 ` Manuel Naranjo
2008-03-31 3:31 ` Marcel Holtmann
2008-03-31 3:39 ` Manuel Naranjo
2008-03-31 3:56 ` Marcel Holtmann
2008-03-31 4:01 ` Manuel Naranjo
2008-03-31 4:09 ` Marcel Holtmann
2008-03-31 13:58 ` Manuel Naranjo
2008-03-31 4:04 ` Denis KENZIOR
2008-03-31 13:33 ` Manuel Naranjo
2008-04-02 16:05 ` Pierre-Yves Paulus
2008-04-02 16:13 ` Manuel Naranjo
2008-04-02 16:22 ` Pierre-Yves Paulus [this message]
2008-04-02 23:37 ` Denis KENZIOR
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=47F3B2C3.5050000@idlum.be \
--to=py@idlum.be \
--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