On 9.11.2010 01:49, Steven Rostedt wrote: > On Sun, 2010-10-31 at 18:05 -0400, Arnaud Lacombe wrote: >> Hi, > >>> But you are right. After KS and Plumbers, I'll work on doing something >>> like that. That can probably solve some of the other issues I'm having >>> (still keeping too many modules enabled). >>> >> I have some work in progress in this area: cleanup, better split >> between the kconfig backend and frontend, and eventually a perl >> binding. That would all be an interesting goal for .38 :-) >> >> Currently I got the parser working within perl, but I'm not really >> really sure of what I can currently do with it and how the whole thing >> interface to one another :) > > Let me know what you got, I would really like localmodconfig to have > this back end. It should really help get a minimal config as well. What information does localmodconfig need? A list of config options and their computed dependencies and a flag for each option if it has prompt, anything else? So a scripts/kconfig/conf --dump-kconfig that would produce such flat list should suffice, without the complexity of having to build a perl binding first (and would be usable from bash/awk/python scripts as well). What do you think? 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
