From: Roman Zippel <zippel@linux-m68k.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: what means duplicate "config" entries in Kconfig file?
Date: Wed, 9 Apr 2003 21:54:12 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0304092115160.5042-100000@serv> (raw)
In-Reply-To: <Pine.LNX.4.44.0304091237490.28112-100000@dell>
Hi,
On Wed, 9 Apr 2003, Robert P. J. Day wrote:
> the two options X86_VISWS and X86_VOYAGER are simple "bool"s
> representing the (radio-box) subarchitecture type.
>
> the first seems to represent a dependency of *neither* of those
> two listed options, while the second config *depends* on one of
> them.
>
> how exactly do you reconcile what looks like contradictory
> dependencies for the same config entry?
With config entries you mainly define menu prompts and defaults.
Dependencies are now properties of these prompts and defaults. With "if"
you can define dependencies which are only attached to these prompts or
defaults. Dependencies defined with "depends on" are attached to all of
them defined within this menu entry.
Internally this becomes a simple list:
config MCA
+- prompt "MCA support"
| +- depends on !(X86_VISWS || X86_VOYAGER)
+- default y
+- depends on X86_VOYAGER
If you enable the debug option of xconfig, this list is displayed with the
help text.
bye, Roman
prev parent reply other threads:[~2003-04-09 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 12:30 Robert P. J. Day
2003-04-09 16:08 ` Randy.Dunlap
2003-04-09 16:23 ` Roman Zippel
2003-04-09 16:43 ` Robert P. J. Day
2003-04-09 19:54 ` Roman Zippel [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=Pine.LNX.4.44.0304092115160.5042-100000@serv \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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®