> >The last time this was brought up someone said that you would need
> >to put each config option in its own *.h file.
Yes. The whole point about Makefile rules and dependencies is that you
can specify exactly what depends on what. If an option does not
depend on anything else, put it in its own file.
The main problems with this approach are not really problems IMHO:
many tiny files - okay, we already have these. :-)
A need to change just about every file in the source tree - this has
to be done just once; instead of a patch distribute a script that
makes the changes automatically.
Explosion in dependencies - no, the typical source file in the kernel
references just three or four CONFIG_xxx items. This is precisely why
autoconf.h is severely broken.
> >That's very gross I know but I think it would be very fast
> >with cpp watching the timestamps instead of make.
> No thanks, it should be make's job to determine what gets "made"
Yes, that's make's job. Make is not really that slow; I suspect the
many recursive make invocations cost more time than the dependancy
checks.
olaf
--
___ Olaf.Titz@inka.de or @{stud,informatik}.uni-karlsruhe.de ____
__ o <URL:http://www.inka.de/~bigred/> <IRC:praetorius>
__/<_ >> Just as long as the wheels keep on turning round
_)>(_)______________ I will live for the groove 'til the sun goes down << ____