On 19.11.2011 08:52, konrad.gaisler wrote: > On 11/19/2011 07:23 AM, Arnaud Lacombe wrote: >> On Fri, Nov 18, 2011 at 5:51 PM, konrad.gaisler<konrad@xxxxxxxxxxx> wrote: >>> As an example, apply the patch, then add to<top>/Kconfig the lines: >>> >>> subsource "arch/sparc/Kconfig" "." ".config_sparc" "SPARC config" SPARC_ >>> CONFIG_ >>> subsource "arch/mips/Kconfig" "." ".config_mips" "MIPS config" MIPS_ CONFIG_ >>> >> ETOOMUCHARGUMENT! >> >> I wonder if we could not get all these parameters specified >> dynamically in the Kconfig. This would replace the `mainmenu' entry >> ala: >> >> config >> title "Linux ..." >> prefix "CONFIG_" >> file .config >> endconfig > Yes maybe it can be done that way. Personally I think it is > more difficult. A <command> <argument> syntax fits well into the existing Kconfig language and it more readable, as you don't have to count the position of the arguments and check their meaning in the documentation. Michal -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
