From: Dave Mielke <dave@mielke.cc>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Setting a PIN without a GUI.
Date: Mon, 23 Jul 2007 14:43:09 -0400 [thread overview]
Message-ID: <20070723184309.GP11031@beta.private.mielke.cc> (raw)
In-Reply-To: <1185213219.7111.48.camel@violet>
[quoted lines by Marcel Holtmann on 2007/07/23 at 19:53 +0200]
>you have to provide a passkey agent that will handle the PIN request.
>The bluez-utils source contains an example passkey-agent.c that we used
>for testing.
Can a variant of that tool run as a thread which lives for the duration of the
connect attempt? If so, does it need to stay running until the close or can it
be terminated as soon as the connect succeeds?
I tried to compile it with -I/usr/include/dbus-1.0 and -I/usr/lib/dbus-1.0, and
still got VERSION not defined.
Is there a tool which should give me the right compile and link flags?
--
Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me
EMail: dave@mielke.cc | Canada K2A 1H7 | if you're concerned about Hell.
http://FamilyRadio.com/ | http://Mielke.cc/bible/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-07-23 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 17:49 [Bluez-devel] Setting a PIN without a GUI Dave Mielke
2007-07-23 17:53 ` Marcel Holtmann
2007-07-23 18:43 ` Dave Mielke [this message]
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=20070723184309.GP11031@beta.private.mielke.cc \
--to=dave@mielke.cc \
--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