This is -not- the situation now, and it will never be the situation.
Did you read drivers/net/Makefile.lib ?
Another example, take a look at drivers/video/Config.in. We actually do
not need those hideously long if statements "if foofb or barfb or bazfb"...
Makefile rules clean that shit up nicely.
> It would be really great if, some day, you just add your source
> file(s) to drivers/net and that is the only thing you ever touch. You
> DO NOT touch Makefiles, you DO NOT touch Config.in files, you DO NOT
> add Config.help entries.
You are preaching to the choir. ;-)
> The Makefile rules are auto-generated from keys in the *.c file(s), as
> are the Config.in and help entries. Ie. cp driver.[ch]
> linux/drivers/net and then simply rebuild the tree.
Close... Check out this thread from December. I agree with Linus
we need metadata files (driver.conf), not yanking all that info out
of the source code.
To sum, Makefile rules are better than Config.in garbage because it can
be far more modular, and more resistant to breakage. But, for the
longer term, we want 8139too.conf and lance.conf and...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/