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: Tue, 05 Aug 2014 11:48:30 +0100	[thread overview]
Message-ID: <1407235710.6981.84.camel@ted> (raw)
In-Reply-To: <30DC4EDFD798C94083F3E083754532CCC9B1AF@G08CNEXMBPEKD02.g08.fujitsu.local>

On Tue, 2014-08-05 at 10:23 +0000, biannm@cn.fujitsu.com wrote:
> > On Tue, 2014-08-05 at 05:57 +0000, biannm@cn.fujitsu.com wrote:
> > > If $B != $S is supported, there is not a problem.
> > > When we rebuild a recipe where $B != $S is not supported, although
> > > tasks will be redone, the source files will not be rebuild if we just
> > change the libdir.
> > 
> > It depends on the Makefiles. Some work well, some don't.
> 
> Yes, i think so too.
> And, does you mean this is not the problem of yocto, we don't need care it?

Well, you could force the build system to wipe out and reconstruct ${S}
any time there was a change. For better or worse we've effectively
decided that its too much overhead for day to day use. If you need that
level of determinism, you can wipe TMPDIR.

> > > Does you mean that we just make this recipe to support  $B != $S in this
> > case.
> > 
> > Yes, that would be one way to solve the problem.
> 
> But how can i divide those recipe from normal one,
> it's not easy to understand for yocto developer because the rebuild will not report any message in this case.

Its a limitation of the software we're building so its not something its
easy for "Yocto" to fix...

Cheers,

Richard




  reply	other threads:[~2014-08-05 10:48 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
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 [this message]
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=1407235710.6981.84.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.