From: jim.cromie@gmail.com
To: Martin Herdeis <martinherdeis@gmx.de>
Cc: Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: make menuconfig
Date: Thu, 25 Mar 2021 12:52:36 -0600 [thread overview]
Message-ID: <CAJfuBxy2ZnXPTDZOHr_Xve18deGcvEGuYxXCqQOSRnaCmvFndQ@mail.gmail.com> (raw)
In-Reply-To: <trinity-f42a0827-d784-4250-9f50-cb82b81a3836-1616267220449@3c-app-gmx-bs17>
[-- Attachment #1.1: Type: text/plain, Size: 1757 bytes --]
On Sat, Mar 20, 2021 at 1:07 PM Martin Herdeis <martinherdeis@gmx.de> wrote:
> Hello,
>
> I am trying to learn more about the kernel build system and due to that I
> tried the following in the top level Kconfig file right at the beginning:
>
> config FOO
> tristate
> prompt "FOO"
> config BAR
> tristate "BAR" if FOO
>
i suspect that last line - it feels like a thinko,
combining a declaration and a dependency.
moreover, `ack tristate` (recursive grep w other nicetohaves)
shows 0 such uses.
heres typical usage
drivers/infiniband/hw/hfi1/Kconfig
3: tristate "Intel OPA Gen1 support"
drivers/infiniband/hw/vmw_pvrdma/Kconfig
3: tristate "VMware Paravirtualized RDMA Driver"
drivers/infiniband/hw/mlx4/Kconfig
3: tristate "Mellanox ConnectX HCA support"
drivers/infiniband/hw/mthca/Kconfig
3: tristate "Mellanox HCA support"
drivers/infiniband/hw/qib/Kconfig
3: tristate "Intel PCIe HCA support"
> default y
>
> Then I do a make menuconfig and choose the config option FOO with "m" then
> the config option BAR shows up with "y". if I exit and save this
> constellation m/y shows up in the .config file. But as I understand the
> logic the value of the config option FOO defines the upper level for the
> value of the config option BAR.
>
> When I do just a make menuconfig again both options show up as m even
> though in the .config file they are still saved as y/m.
>
> Is that a problem with the default value of BAR? Am I not supposed to give
> it a default value out of range when FOO is m?
>
>
> Thank you,
>
> Martin
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
[-- Attachment #1.2: Type: text/html, Size: 3091 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2021-03-25 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 19:07 make menuconfig Martin Herdeis
2021-03-25 18:52 ` jim.cromie [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=CAJfuBxy2ZnXPTDZOHr_Xve18deGcvEGuYxXCqQOSRnaCmvFndQ@mail.gmail.com \
--to=jim.cromie@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=martinherdeis@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).