Skip to contentSkip to conversation

linux kernel config converter

DISCUSSION Giacomo Catenazzi 4 participants 5 messages Feb 21, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 9 lines · Jeff Garzik
Quoted 6 lines · Erik Andersen

I like this. It's simple, its clean, and it keeps all the information in one spot. I think we can go a bit farther here and add in a list of the .c files that enabling this feature should add to the Makefile (per the current
obj-$(CONFIG_FOO) += foo.o
stuff in the current Makefile).

Quoted 4 lines

Seriously, yep, that's exactly where we eventually want to be: all config, makefile, and help text info in one place. To add a new net driver, I want to be able to simply add two files, driver.c and driver.conf, and be done with it.

with kbuild-2.5 this can be done easy. We should maintain the syntax of kbuild-2.5 (or a subset).

But the makefile/makefile.in will remain: not all code in kernel is drivers, and for the non drivers makefile/config.in IMHO it is better to have 'central' (per directory/per type) config and makefile files.

giacomo

#2 lore raw
In reply to a message not in the archive
Quoted 17 lines · Giacomo Catenazzi
Quoted 9 lines · Jeff Garzik
Quoted 6 lines · Erik Andersen

I like this. It's simple, its clean, and it keeps all the information in one spot. I think we can go a bit farther here and add in a list of the .c files that enabling this feature should add to the Makefile (per the current
obj-$(CONFIG_FOO) += foo.o
stuff in the current Makefile).

Quoted 4 lines

Seriously, yep, that's exactly where we eventually want to be: all config, makefile, and help text info in one place. To add a new net driver, I want to be able to simply add two files, driver.c and driver.conf, and be done with it.

Quoted 7 lines

with kbuild-2.5 this can be done easy. We should maintain the syntax of kbuild-2.5 (or a subset).

But the makefile/makefile.in will remain: not all code in kernel is drivers, and for the non drivers makefile/config.in IMHO it is better to have 'central' (per directory/per type) config and makefile files.

yes and no :)

We do not want to limit one-driver one-file, just support it.

And, makefile information needs to be included along with config information. For a more realistic example, when I add a new net driver, I would modify
drivers/net/new-driver.c
drivers/net/net-drivers.conf

and the second file includes the makefile rules necessary to build things.

For directories like kernel/* and mm/* and arch/*, I imagine that down the road we will want kernel.conf and mm.conf too, though right now they would probably remain as makefiles...

If you look closely at the problem, you will see there is no fundamental reason why we cannot package makefile rules like we want to package config information.

Jeff

Signature · 4 lines
Jeff Garzik      | "Why is it that attractive girls like you
Building 1024    |  always seem to have a boyfriend?"
MandrakeSoft     | "Because I'm a nympho that owns a brewery?"
                 |             - BBC TV show "Coupling"
#3 lore raw

On Thu, 21 Feb 2002, Jeff Garzik wrote:

| For directories like kernel/* and mm/* and arch/*, I imagine that down
| the road we will want kernel.conf and mm.conf too, though right now they
| would probably remain as makefiles...

I agree. I was just looking for linux/kernel/config.in a couple of days ago.
Instead, I had to look in _many_ arch/<archxxx>/config.in files. Bah.

Signature · 1 line
~Randy
#4 lore raw
In reply to a message not in the archive
Quoted 8 lines · Jeff Garzik
Quoted 1 line

For directories like kernel/* and mm/* and arch/*, I imagine that down the road we will want kernel.conf and mm.conf too, though right now they would probably remain as makefiles...

If you look closely at the problem, you will see there is no fundamental reason why we cannot package makefile rules like we want to package config information.

I agree that in most case (drivers) it is the right thing. But for kernel/, arch/ there are no simple way to tell:
"this makefile rule belong to this configuration". In such cases we should not split makefiles and configurations in an artificial way.
We should not generalize and split configuration and makefile just because in most case it is the right thing.

[ Some Makefile define at the beginning some flags that
should be used for all driver in such subdir. These info should be in a 'main' .conf (main = where normal user would check, without grep to all .conf)
]

giacomo

#5 lore raw
In reply to a message not in the archive
Quoted 2 lines · Giacomo Catenazzi

But for kernel/, arch/ there are no simple way to tell:
"this makefile rule belong to this configuration".

Sure you can. You can generate makefiles from any source you wish... kernel/* and mm/* are actually easy examples, arch/* is much more difficult.

Signature · 4 lines
Jeff Garzik      | "Why is it that attractive girls like you
Building 1024    |  always seem to have a boyfriend?"
MandrakeSoft     | "Because I'm a nympho that owns a brewery?"
                 |             - BBC TV show "Coupling"