Where is the end of "menuconfig" entry scope?

Where is the end of "menuconfig" entry scope?

[Filip Honckiewicz]

Hi!
I just want to ask you - Great Developers - where is the end of
"menuconfig" entry scope? I read kconfig-language.txt, but there are
some lacks in documentation, so I don't know which (and why?)
suboption is the last suboption of menuconfig. Is this defined by end
of Kconfig file or what?

Greetings
Filip Honckiewicz

Re: Where is the end of "menuconfig" entry scope?

[Michal Marek]

On 15.1.2011 22:35, Filip Honckiewicz wrote:
> I just want to ask you - Great Developers - where is the end of
> "menuconfig" entry scope? I read kconfig-language.txt, but there are
> some lacks in documentation, so I don't know which (and why?)
> suboption is the last suboption of menuconfig. Is this defined by end
> of Kconfig file or what?

"menuconfig" does not start a block, semantically it is equivalent to
"config". Kconfig is able to derive the menu structure from
dependencies, see "Menu structure" in kconfig-language.txt,
config/menuconfig only influence how the resulting menu is rendered in
the frontends. E.g. 'make nconfig' and 'make menuconfig' frontends
display the menu like

[*] Foo
[ ]   Bar
[ ]   Baz

if Foo is "config", and

[*] Foo  --->
(Bar and Baz hidden in the submenu)

if Foo is "menuconfig".

hth,
Michal

Re: Where is the end of "menuconfig" entry scope?

[Filip Honckiewicz]

2011/1/17 Michal Marek <mmarek@suse.cz>:
> On 15.1.2011 22:35, Filip Honckiewicz wrote:
>> I just want to ask you - Great Developers - where is the end of
>> "menuconfig" entry scope? I read kconfig-language.txt, but there are
>> some lacks in documentation, so I don't know which (and why?)
>> suboption is the last suboption of menuconfig. Is this defined by end
>> of Kconfig file or what?
>
> "menuconfig" does not start a block, semantically it is equivalent to
> "config". Kconfig is able to derive the menu structure from
> dependencies, see "Menu structure" in kconfig-language.txt,
> config/menuconfig only influence how the resulting menu is rendered in
> the frontends. E.g. 'make nconfig' and 'make menuconfig' frontends
> display the menu like
>
> [*] Foo
> [ ]   Bar
> [ ]   Baz
>
> if Foo is "config", and
>
> [*] Foo  --->
> (Bar and Baz hidden in the submenu)
>
> if Foo is "menuconfig".
>
> hth,
> Michal
>

Thanks!

It helped me a lot and now it's clear. Your example shows everything.
In kconfig-language.txt there is:
 "This is similar to the simple config entry above, but it also gives
a hint to front ends, that all suboptions should be displayed as a
separate list of options." and this "suboptions" fool me that if
there're suboptions than there has to be ending of menuconfig entry;)

Filip

Re: Where is the end of "menuconfig" entry scope?

[Yann E. MORIN]

Filip, All,

On Monday 17 January 2011 23:39:17 Filip Honckiewicz wrote:
> It helped me a lot and now it's clear. Your example shows everything.
> In kconfig-language.txt there is:
>  "This is similar to the simple config entry above, but it also gives
> a hint to front ends, that all suboptions should be displayed as a
> separate list of options." and this "suboptions" fool me that if
> there're suboptions than there has to be ending of menuconfig entry;)

Maybe expressing this in a more understandable way, such as:

  The menuconfig scope ends with the last config options that depends
  on that menuconfig entry.

Is that more comprehensible? If so, maybe suggest a patch to clear up the
confusion.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

Re: Where is the end of "menuconfig" entry scope?

[Michal Marek]

On 17.1.2011 23:50, Yann E. MORIN wrote:
> Filip, All,
> 
> On Monday 17 January 2011 23:39:17 Filip Honckiewicz wrote:
>> It helped me a lot and now it's clear. Your example shows everything.
>> In kconfig-language.txt there is:
>>  "This is similar to the simple config entry above, but it also gives
>> a hint to front ends, that all suboptions should be displayed as a
>> separate list of options." and this "suboptions" fool me that if
>> there're suboptions than there has to be ending of menuconfig entry;)
> 
> Maybe expressing this in a more understandable way, such as:
> 
>   The menuconfig scope ends with the last config options that depends
>   on that menuconfig entry.

Then such sentence would have to be added to "config" as well. Or just
point people to the Menu structure chapter.

Michal

Re: Where is the end of "menuconfig" entry scope?

[Filip Honckiewicz]

2011/1/18 Michal Marek <mmarek@suse.cz>:
> On 17.1.2011 23:50, Yann E. MORIN wrote:
>> Filip, All,
>>
>> On Monday 17 January 2011 23:39:17 Filip Honckiewicz wrote:
>>> It helped me a lot and now it's clear. Your example shows everything.
>>> In kconfig-language.txt there is:
>>>  "This is similar to the simple config entry above, but it also gives
>>> a hint to front ends, that all suboptions should be displayed as a
>>> separate list of options." and this "suboptions" fool me that if
>>> there're suboptions than there has to be ending of menuconfig entry;)
>>
>> Maybe expressing this in a more understandable way, such as:
>>
>>   The menuconfig scope ends with the last config options that depends
>>   on that menuconfig entry.
>
> Then such sentence would have to be added to "config" as well. Or just
> point people to the Menu structure chapter.
>
> Michal
>

I agree with Michal. It makes no sense. But maybe remove "suboptions"
and change whole sentence to something like this:
"This is similar to the simple config entry above, but it also gives a
hint to front ends, that all other options that depends on this entry
should be displayed as a
separate list of options."

and maybe add Michal's example to "Menu structure" chapter to show
this little difference between config and menuconfig. Or maybe not;)

Sorry for my english.
Filip