All right! Then I will plan for my "yacc + C" configuration program
to replace all flavors of configuration.
There are about 3000 lines of Config.in files. First I plan to write
a drop-in replacement for Configure / Menuconfig / xconfig. Then once
there is a single front end, I can design a new incompatible syntax
(several other people have ideas about the syntax too).
I agree about needing a "no ncurses" UI.
> I certainly hope the program is small enough that it doesn't take all
> that long to compile.
No problem.
I have a "test-config" demo program that has a parser and some of the
"make config" UI code. I measured compile times on two machines,
my super-slow 486/SLC and my ISP's Pentium 90 MHz. On both machines,
compiling my "test-config" demo program takes about 0.6% of the time
needed for a full kernel build. So if a user has a machine that takes
fifteen minutes to build a kernel, such as my ISP's Pentium 90 MHz,
"make config" will take about 6 seconds to compile and link. That is
with -O2 -Wall turned on.
This is obviously just ballpark because I haven't finished writing all
the code yet -- in particular I haven't written any "save" routines.
Regards,
Michael Chastain
<mailto:mec@shout.net>
"love without fear"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu