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.
-- Steve
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
Hi,
On Thu, Nov 25, 2010 at 10:45 AM, Michal Marek <[email protected]> wrote:
> 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?
>
Just as a FYI, the output of zconfdump() does not respect the kconfig
syntax. I've got some patches to fix that, but I've not been able to
touch them since a few weeks now.
- Arnaud
On 25.11.2010 17:21, Arnaud Lacombe wrote:
> Hi,
>
> On Thu, Nov 25, 2010 at 10:45 AM, Michal Marek <[email protected]> wrote:
>> 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?
>>
> Just as a FYI, the output of zconfdump() does not respect the kconfig
> syntax. I've got some patches to fix that, but I've not been able to
> touch them since a few weeks now.
I'm not saying zconfdump() has to be used or that it has to follow the
kconfig syntax (*), just that a pipe interface between the C kconfig and
a Perl script might be easier to implement and use :-).
(*) Although using a subset of the kconfig syntax would be a good idea
definitely.
Michal