[yocto] Bitbake on live (uncommitted) code

[Brad Litterell]

Thank you!

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?

Thanks,
Brad
________________________________________
From: Paul Eggleton [paul.eggleton at linux.intel.com]
Sent: Friday, September 13, 2013 2:55 AM
To: Brad Litterell
Cc: Chris Larson; yocto at yoctoproject.org
Subject: Re: [yocto] Bitbake on live (uncommitted) code

On Thursday 12 September 2013 17:23:53 Chris Larson wrote:
> On Thu, Sep 12, 2013 at 4:53 PM, Brad Litterell <brad at evidence.com> wrote:
> > I've grown to really appreciate bitbake for compiling code from a myriad
> > of sources, however, what is the recommended course for source I am
> > currently doing live development on?  My code base lives in a couple of
> > git
> > repos that do NOT map one-to-one with recipes and I don't really want to
> > store the source mixed in with the recipe meta data anyway, nor do I want
> > to be forced to commit it to git just to do a build.
> >
> >  Currently I run a pre-bitbake script that creates a tarball out of the
> >
> > source, but that is easy to forget and makes building a new image a two
> > step proces.  Since it is a build step I'd like it to be done by bitbake.
> >
> >  Is there a recommended way to go about this?
>
> See externalsrc.bbclass.

Also the manual section that talks about using it:

http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#building-software-from-an-external-source

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre