From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] bluez hcid v3.31 main.conf
Date: Thu, 22 May 2008 18:09:24 -0500 [thread overview]
Message-ID: <01e501c8bc60$e20638c0$6701a8c0@freqonedev> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 759 bytes --]
On startup, hcid attempts to load_config(CONFIGDIR "main.conf"). However, main.conf is missing. This may have been a recent change in that in hcid.h, HCID_CONFIG_FILE refers to CONFIGDIR "hcid.conf".
When I attempt to substitute HCID_CONFIG_FILE to load_config, load_config chokes on what is in that file.
So, what is/should be contained in main.conf? Is the correct, or what should it be? (In general, using a "magic filename" like "main.conf" is not a great practice, and perhaps makes the code base harder to maintain, especially when a #define with a similar purpose already exists in the headers...)
Thanks in advance,
David Stockwell
BTW, to those who are going to be there, enjoy Helsinki...one of the few places I have not yet been!
[-- Attachment #1.2: Type: text/html, Size: 1561 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- 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 reply other threads:[~2008-05-22 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 23:09 David Stockwell [this message]
2008-05-22 23:16 ` [Bluez-devel] bluez hcid v3.31 main.conf 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='01e501c8bc60$e20638c0$6701a8c0@freqonedev' \
--to=dstockwell@frequency-one.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