All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "biannm@cn.fujitsu.com" <biannm@cn.fujitsu.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [Question]Does poky rebuild source when only makefile was modified
Date: Mon, 04 Aug 2014 11:24:02 +0100	[thread overview]
Message-ID: <1407147842.6981.52.camel@ted> (raw)
In-Reply-To: <30DC4EDFD798C94083F3E083754532CCC9AAA9@G08CNEXMBPEKD02.g08.fujitsu.local>

On Mon, 2014-08-04 at 10:01 +0000, biannm@cn.fujitsu.com wrote:
> Hi,
> 
>  Usually, if only makefile is modified, "make" will not rebuild source.
>  Does poky rebuild source in the following case.
> 
>  1. build a recipe
>  2. modify the bb file of this recipe, which will cause only makefile to be modified.
>     Ex. set a new path to libdir
>  3. rebuild this recipe without doing cleansstate before

This change to libdir would change the checksum of the configure task
and the configure task would execute. Assuming this is an autotools
recipe (where B != S is supported), it would wipe out ${B} due to the
change and rebuild everything from the configure step onwards.

Cheers,

Richard



  reply	other threads:[~2014-08-04 10:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 10:01 [Question]Does poky rebuild source when only makefile was modified biannm
2014-08-04 10:24 ` Richard Purdie [this message]
2014-08-05  1:35   ` biannm
2014-08-05  2:24     ` Khem Raj
2014-08-05  3:13       ` biannm
2014-08-05  5:06         ` Khem Raj
2014-08-05  5:57           ` biannm
2014-08-05  6:29             ` Khem Raj
2014-08-05  9:44             ` Richard Purdie
2014-08-05 10:23               ` biannm
2014-08-05 10:48                 ` Richard Purdie
2014-08-18  6:42                   ` biannm

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=1407147842.6981.52.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=biannm@cn.fujitsu.com \
    --cc=poky@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.