Messages in this thread |  | | | Date | Wed, 3 Jun 1998 10:30:49 +0200 | | From | Pavel Machek <> | | Subject | More kernel configs on single machine (was Re: [IDEA] Developers:) |
| |
Hi!
> I propose the following for linux to support 'configuration names' too: > > - Add a way in config/menuconfig/xconfig to enter a 'Configuration > name'
Very easy. In fact, I'm using it from 2.1.80 or so.
> - Use this name as postfix for .config, e.g. instead of > /usr/src/linux/.config the configuration file shall be named > /usr/src/linux/.config.NAME. The default configuration could be saved > in /usr/src/linux/.defaultname
Why not kernel configuration stays in .config, but one of first entries is CONFIG_COMMENT = "Elf" or something like that? You then safe mess with default name.
You are right that user should be able to specify CONFIG=XXX with make.
(You can leave it up to user how [s]he wants to call his .config files.)
Also, .config really should NOT NOT NOT begin with . - that file should not be hidden.
> - Add a elegant way using the existing "oldconfig" mechanism to configure > the kernel tree for different named configurations, e.g. > make CONFNAME=myothermachine oldconfig > Or even better: > make CONFFILE=/some/where/else/config-file oldconfig > The same variables could be used for config/menuconfig/xconfig to allow > editing non-default configurations.
This would be really nice!
Also note that mec@shout.net already did this. He went few steps further and separated source/bin trees, so you could compile for two different setups without rebuilding all sources each time. > What does the list think?
Parts of this are already done. I really think that mec's dancing makefiles should be merged as soon as possible.
Pavel
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
|  |