From: Roman Zippel <zippel@linux-m68k.org>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where's the documentation for Kconfig?
Date: Thu, 31 Oct 2002 15:43:26 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0210311452531.13258-100000@serv> (raw)
In-Reply-To: <20021031134308.I27461@parcelfarce.linux.theplanet.co.uk>
Hi,
On Thu, 31 Oct 2002, Matthew Wilcox wrote:
> I'm just looking over the new arch/parisc/Kconfig trying to make sure that
> it got translated correctly, but I can't find any documentation.
http://www.xs4all.nl/~zippel/lc/
> Some of
> the Kconfig files refer to "the Configure script" -- what Configure
> script? Some of them refer to Documentation/kbuild/config-language.txt
> -- which describes the old one. Most don't tell you where to find
> the description.
The comments are still the same as before and need to be corrected
manually.
> What's the difference between `help' and `---help---'?
None. Actually you can insert lots of '---' as separators almost anywhere
you want. The converter used ---help--- for large help texts to separate
them a bit better from the other options.
> What's the new idiom for define_bool?
Here a small howto for CML1 users.
cml1:
bool/tristate/int/... /prompt/ /symbol/ /word/
kconfig:
config /symbol/
bool /prompt/
default /word/
(bool/tristate have now defaults as well.)
cml1:
define_bool /symbol/ /word/
kconfig:
config /symbol/
bool
default /word/
cml1:
dep_bool /prompt/ /symbol/ /dep/ ...
kconfig:
config /symbol/
bool /prompt/
depends on /dep/=y && ...
cml1:
dep_mbool /prompt/ /symbol/ /dep/ ...
dep_int...
kconfig:
config /symbol/
bool /prompt/
depends on /dep/ && ...
cml1:
choice /prompt/ /word/ /word/
kconfig:
choice
prompt /prompt/
default /symbol/
config
....
endchoice
Especially the choice statement became much more powerful. Multiple
defaults are possible, every choice value can have further dependencies
and it can be tristate.
Dependencies are very close to the old behaviour with only some small
differences, e.g. '-a'/'-o' are simply '&&'/'||', "CONFIG_FOO"="y" becomes
FOO=y and only FOO has the same meaning as in dep_tristate. Important
here is that the undefined state is gone and kconfig will soon start
emit warnings for undefined symbols used in expressions.
bye, Roman
next prev parent reply other threads:[~2002-10-31 14:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 13:43 Matthew Wilcox
2002-10-31 14:43 ` Roman Zippel [this message]
2002-10-31 15:27 ` Christoph Hellwig
2002-10-31 16:03 ` Roman Zippel
2002-11-01 8:23 ` Rusty Russell
2002-11-01 12:52 ` Russell King
2002-11-01 13:50 ` Roman Zippel
2002-11-01 19:31 ` Russell King
2002-11-01 20:30 ` Tom Rini
2002-11-01 20:35 ` Russell King
2002-11-01 20:42 ` Tom Rini
2002-11-01 20:46 ` Russell King
2002-11-01 23:32 ` Tom Rini
2002-11-01 23:52 ` Roman Zippel
2002-11-02 0:07 ` Tom Rini
2002-11-02 0:46 ` Roman Zippel
2002-11-01 20:35 ` Roman Zippel
[not found] ` <20020625221306.GA439@free.fr>
[not found] ` <Pine.LNX.4.44.0211021254420.6949-100000@serv>
2002-11-02 13:20 ` Kconfig (qt) -> Gconfig (gtk+) Romain Lievin
2002-11-02 14:45 ` Roman Zippel
2002-11-02 18:56 ` qconf buglet James H. Cloos Jr.
2002-11-02 19:48 ` Roman Zippel
2002-11-02 23:40 ` James H. Cloos Jr.
2002-11-02 13:51 ` Where's the documentation for Kconfig? Erik Andersen
2002-11-02 19:26 ` Roman Zippel
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=Pine.LNX.4.44.0210311452531.13258-100000@serv \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.org \
/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
all inboxes | Powered by JetHome®