Greg Banks <[EMAIL PROTECTED]>:
> Wouldn't it be simpler to allow the rules file to not specify
> a `default'? The runtime semantics of this would be that the first
> unsuppressed choice is displayed as the default. So Keith could
> write:
>
> choices kernel_format # The format that the kernel is to be compiled in
> BZIMAGE ZIMAGE VMLINUZ VMLINUX
>
> unless IA64 suppress VMLINUZ BZIMAGE ZIMAGE
>
> The default choice the user sees is the first of BZIMAGE, ZIMAGE,
> VMLINUZ or VMLINUX which is supported on the chosen architecture.
> On IA64 the only choice would be VMLINUX.
We have a winner...
I have implemented this. The exact semantics are as follows:
1. If no default is specified at compile time, the default is the
menu's first symbol.
2. At menu instantiation time, the actual default is found by starting at
the compiled-in default and searching forward to find a visible symbol.
If such a viable symbol is found it is used as the default (set to y).
3. If no such visible symbol is found, the suppression flag is turned off
and the compiled-in default is used as the default (set to y).
--
<a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
Fantastic doctrines (like Christianity or Islam or Marxism) require unanimity
of belief. One dissenter casts doubt on the creed of millions. Thus the fear
and the hate; thus the torture chamber, the iron stake, the gallows, the labor
camp, the psychiatric ward. -- Edward Abbey
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel
