public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: mmarek@suse.cz, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Makefile: allow no update .config build
Date: Thu, 28 Mar 2013 10:13:50 -0700	[thread overview]
Message-ID: <51547A4E.4010600@infradead.org> (raw)
In-Reply-To: <1364455686-18930-1-git-send-email-lig.fnst@cn.fujitsu.com>

On 03/28/13 00:28, liguang wrote:
> if we pull some commits from other git repo
> which bring in a few CONFIG_* options, then
> we have to build all again, but we do assure
> these options are not interesting for us,
> so the long waiting build will be offending.
> this change help us to avoid all-build.
> 
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
> ---
>  Makefile |    9 +++++++++
>  1 files changed, 9 insertions(+), 0 deletions(-)
> 
> diff --git a/Makefile b/Makefile
> index 54d2b2a..d10e505 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -106,6 +106,12 @@ ifeq ("$(origin W)", "command line")
>    export KBUILD_ENABLE_EXTRA_GCC_CHECKS := $(W)
>  endif
>  
> +# KBUILD_NCU is set to do not update .config even
> +# a few new CONFIG_* options appeared
> +ifeq ("$(origin NCU)", "command line")
> +  KBUILD_NCU := $(NCU)
> +endif
> +
>  # That's our default target when none is given on the command line
>  PHONY := _all
>  _all:
> @@ -540,8 +546,10 @@ $(KCONFIG_CONFIG) include/config/auto.conf.cmd: ;
>  # with it and forgot to run make oldconfig.
>  # if auto.conf.cmd is missing then we are probably in a cleaned tree so
>  # we execute the config step to be sure to catch updated Kconfig files
> +ifneq ($(KBUILD_NCU), 1)
>  include/config/%.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd
>  	$(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig
> +endif # $(KBUILD_NCU)
>  else
>  # external modules needs include/generated/autoconf.h and include/config/auto.conf
>  # but do not care if they are up-to-date. Use auto.conf to trigger the test
> @@ -1157,6 +1165,7 @@ help:
>  	@echo  '		2: warnings which occur quite often but may still be relevant'
>  	@echo  '		3: more obscure warnings, can most likely be ignored'
>  	@echo  '		Multiple levels can be combined with W=12 or W=123'
> +	@echo  '  make NCU=1 [targets] no .config udate'

	                                          update

>  	@echo  ''
>  	@echo  'Execute "make" or "make all" to build all targets marked with [*] '
>  	@echo  'For further info see the ./README file'
> 


-- 
~Randy

  reply	other threads:[~2013-03-28 18:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  7:28 [PATCH] Makefile: allow no update .config build liguang
2013-03-28 17:13 ` Randy Dunlap [this message]
2013-03-29  0:41   ` li guang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51547A4E.4010600@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=lig.fnst@cn.fujitsu.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox