From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Brad Litterell <brad@evidence.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Chris Larson <clarson@kergoth.com>
Subject: Re: Bitbake on live (uncommitted) code
Date: Tue, 17 Sep 2013 19:01:43 +0100 [thread overview]
Message-ID: <6188630.9A4dCK1SRK@helios> (raw)
In-Reply-To: <E51394554A503C4E852F9BEE46B03E8DEFE67D@TI-ODIN.tasernet.com>
Hi Brad,
On Tuesday 17 September 2013 17:48:18 Brad Litterell wrote:
> I've been using externalsrc for a few days now and have a follow on
> question.
>
> It appears that bitbake's state information for the various recipes doesn't
> react to changes in source files in an external source. IOW, when I change
> a file in my external folder I need to perform 3 steps to create a new file
> system that reflects the change:
>
> bitbake <component> -c clean
> bitbake <component>
> bitbake <image>
>
> Is it possible to ask bitbake to be more thorough about detecting file
> changes in external sources and rebuild the affected component
> automatically?
I'm not sure if that would be practical; we'd need to checksum quite a lot of
files for a large source tree. However, there is a slightly simpler method:
bitbake -C compile <component>
bitbake <image>
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-09-17 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 23:53 Bitbake on live (uncommitted) code Brad Litterell
2013-09-13 0:23 ` Chris Larson
2013-09-13 9:55 ` Paul Eggleton
2013-09-13 10:04 ` Hans Beckérus
2013-09-13 10:51 ` Paul Eggleton
2013-09-17 17:48 ` Brad Litterell
2013-09-17 18:01 ` Paul Eggleton [this message]
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=6188630.9A4dCK1SRK@helios \
--to=paul.eggleton@linux.intel.com \
--cc=brad@evidence.com \
--cc=clarson@kergoth.com \
--cc=yocto@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.