[lkml]   [2008]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectAdditional kconfig targets (cloneconfig, nonint_oldconfig etc)
Recently there has been request for a number of new
kconfig related targets.

In general it boils down to the following:

We need to be flexible in what configuration
we start out from and how we apply it.

We need to be able to apply it in following ways:
1) automated - select defaults for all new symbols
=> It is used for "make defconfig, make *_defconfig" today

2) interactive - asking user for all new symbols
and error out if stdin is redirected

3) list unknown - list all new symbols and do not
create a new config

With oldconfig today we have two modes:
-> One mode where we are very chatty and show
all output.
-> And the 'silent' mode where we only start being
chatty when we see a new symbol.

I plan to drop the 'very chatty' mode as I
do not see it usefull.
So in essense 'make oldconfig' and 'make silentoldconfig'
become equal.

The commands we have today for kconfig is:

# Command line variants
make oldconfig
make silentoldconfig
make defconfig
make XXX_defconfig

(The other frontends are left out on purpose).
The challenge here is to come up with a syntax that
allows us to select between the three behaviours,
while keeping backward compatibility.

The best suggestion I have so far is to say that:
a) if defconfig is specified then we use method 1)
b) if oldconfig is specified then we use method 2)
c) if newconfig is specified then we use method 3)

And we add support for a new 'commandline' parameter
'K' so I can say:

make K=/proc/config.gz defconfig
make K=i386_defconfig defconfig
make K=i386_defconfig oldconfig
make K=/proc/config.gz newconfig

So K is used to specify what config file we use
to start out from.

Care should be taken to keep the known good
targets working as before.

Andres Salomon already did some preparational work
for this but I need to find a good way to handle the K=
Dave J also posted patches that is useful for 'newconfig'.

But I wanted to ask for opinions before diving into
implmenting this.


[Random notes..]

# Enviroment variables affecting kconfig

#input files (aparts from the mandatory ones)

 \ /
  Last update: 2008-04-29 20:37    [W:0.282 / U:0.788 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site