[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080502105630.GA20955@uranus.ravnborg.org>
Date: Fri, 2 May 2008 12:56:30 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Jan Engelhardt <jengelh@...ozas.de>
Cc: linux-kbuild <linux-kbuild@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Dave Jones <davej@...emonkey.org.uk>,
Roland McGrath <roland@...hat.com>,
Andres Salomon <dilinger@...ued.net>
Subject: Re: Additional kconfig targets (cloneconfig, nonint_oldconfig etc)
> >(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)
>
> [Where is 1) defined?]
1) automated - select defaults for all new symbols
=> It is used for "make defconfig, make *_defconfig" today
> Ok and these are doing .. what?
> ># Enviroment variables affecting kconfig
> >KCONFIG_ALLCONFIG
Specify input file in .config format to adjust a all*config run
> >KCONFIG_NOSILENTUPDATE
If set then error out if .config is modified
> >KCONFIG_CONFIG
Provide alternative name for .config
> >KCONFIG_OVERWRITECONFIG
If you set KCONFIG_OVERWRITECONFIG in environment, Kconfig will not break
symlinks when .config is a symlink to somewhere else
> >KCONFIG_NOTIMESTAMP
Do not put timestamp in .config
> >KCONFIG_AUTOCONFIG
Provide alternative name for: include/config/auto.conf
> >KCONFIG_AUTOHEADER
Provide alternative name for include/linux/autoconf.h
> Used for..?
All used to hardcode specific values in all*config builds.
> >#input files (aparts from the mandatory ones)
> >all.config
> >allno.config
> >allmod.config
> >allyes.config
> >allrandom.config
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists