Re: recipe dependency on externally built binaries?

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

On Wednesday 31 July 2013 14:04:05 Brian Karcz wrote:
> That's a better answer than I was fearing. I was starting to think that
> Yocto/Poky was only intended to build/assemble versioned or released code.

Most of the time that's the way the system operates, but we're not limited to 
it. The main purpose of the checksums is to allow you to update patches or 
configuration files referred to in SRC_URI, but it works for this case as well.

The only thing I'd advise is to take care that you have mechanisms in place 
that will allow you to easily reproduce older branches. You may already have 
taken care of this; it's just that it's easy to overlook when you point to a 
local file that is not under the control of the build system.

> We are still using Edison. I started going through the cycles of trying to
> upgrade us to Dylan a month or so ago, but ran into an assortment of issues
> regarding udev (at runtime) and some issues with do_fetch/do_unpack not
> executing on an image re-build like they do in Edison. My priority list got
> adjusted a bit, and I had to abandon that effort for a while. This
> information definitely adds a little more to the benefit column of moving
> us forward.

Right. FYI, the traditional way of working with edison and older was just to 
bump PR each time you want the recipe to rebuild.

> Are you saying that if I were to move our build system forward to danny or
> Dylan that the dependency behavior I'm looking for in these recipes would
> start to work as intended? 

Yes, that's correct. If you enable the PR server you can even have PR 
incremented automatically each time a change is made, assuming this helps i.e. 
you have package management enabled on the target.

> Would this behavior survive the use of the rm_work directive?

Yes, it should interact just fine with rm_work.
 
Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre