Re: Image recipes in Yocto 1.4 (dylan-9.0.0)

[Paul Eggleton <paul.eggleton@linux.intel.com>]

Hi Brian,

On Monday 24 June 2013 11:01:31 Brian Karcz wrote:
> I have a question regarding the shared state code optimizations in yocto
> 1.4. I'm in the process of upgrading one of our projects from Edison (6.0)
> to Dylan (9.0.0) and am running into an issue with our existing image
> recipe.
> 
> The recipe brings in files from a "files" directory in the image area. It
> also adds an image preprocess command that takes action on those files in
> the work area. After reading the version 1.4 migration guidelines and
> examining both the old and new builds, it looks like the do_unpack task has
> been optimized out of the way images are built in the new release. The
> files listed in the SRC_URI variable don't get populated in the work
> directory, and actions taken in the image preprocess command fail.
> 
> Is there a way to stop this optimization and have the image build populate
> the work directory as it has in the past?

You should be able to do this in your image recipe:

python () {
        d.delVarFlag("do_fetch", "noexec")
        d.delVarFlag("do_unpack", "noexec")
}

This isn't related to shared state, btw, just that image.bbclass disables 
these tasks by default as of version 1.2 (denzil).

Cheers,
Paul


-- 

Paul Eggleton
Intel Open Source Technology Centre