[...]
> this one file. After I get the kernel to build exactly like it does now
> using the common rules file, I will try to add the features that people
> have asked for. These include:
>
> 1) Ability to make only selected modules
> 2) Ability to put the .o files in a seperate directory tree
> 3) Ability to compile kernels with different sets of configuration
> options from the same source tree (with out having to destroy
> one kernel's .o files to build the other)
> 4) Ability to change config options w/o having to recompile almost
> every file.
> 5) Others I can not remember
>
> I have done a set of patches that implemented item 1, and another set of
> patches that implemented item 2. I did not think that either of these patches
> were very clean, so its good that I am doing them again.
>
> One thing which needs to be done, which I am not trying to do, is change the
> way make config works. It causes so much argument every time it gets
> discussed that I am scared to alter it. Does any brave soul want to try this?
It would be nice to see something like BSD's kernel configuration file. It
keeps all of the configuration information in one file with a moderately
easy syntax. Additionally, if there is demand for it -- I am sure it wouldn't
be much trouble to write a front end that manages it.
The nicest thing about it is that you can set the kernel options (-D's),
modules, and device information all in one (moderately portable) file.
-- Mike
-- Michael Nelson (mikenel@netcom.com) | Real programmers don't comment their Rockville, Maryland | code. It was hard to write, it should BSD/OS, WinNT, OLE2 Development | be hard to understand.