Hi,

Sebastian Henschel wrote:

Your mailer ate the archive, it doesn't look that big, could you include them uncompressed? This would also make it easier to quote them if needed.

Kconfig.if: i prefer this version the most, though it simply does not
work, i do not understand why and perhaps this is due to a bug in
kconfig or badly explained in Documentation/kbuild/kconfig-language.txt
or just my stupidness. my arch is PPC_PMAC. when using
menuconfig/gconfig, i get the correct prompt, but the help text is from
the last config PM defined in this file. so in this case, it is from X86.

This is (currently) correct, kconfig only stores the last the help entry. I want to change this at some point, but I haven't decided about the syntax yet, e.g. which help text should be used for entries, which don't have their own help.


Kconfig.menu: this is basically the same as Kconfig.if, but the docs
say that "The dependency expression <expr> is appended
to all enclosed menu entries". that made me suspicious and thus, the
"if" clauses include menus here.

I can only guess here, but from a dependency point these two are identical:


menu "..."
        depends on <expr>
...
endmenu

if <expr>
...
endif

Kconfig.prompt: the section in the docs about the prompt left me with
the impression that it is possible to define several prompts for the
same "config" entry if there is an "if" clause appended to each prompt.
kconfig warns about prompt redefinitions and only considers the last
defined prompt.

That's correct. A single menu entry can have only one prompt, but a config symbol can have multiple menu entries.


bye, Roman


------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel

Reply via email to