Re: Per-machine DEPENDS

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

On Thursday 17 May 2012 22:07:50 Chris Tapp wrote:
> On 17 May 2012, at 21:27, Paul Eggleton wrote:
> > On Thursday 17 May 2012 21:10:10 Chris Tapp wrote:
> >> Is it possible to have the (R)DEPENDS list vary depending on the machine
> >> being built?
> >> 
> >> For example, I want 'this-bit' to be included for a 'machine-1' build,
> >> but
> >> not 'machine-2'.
> >> 
> >> Something like:
> >> 
> >> DEPENDS = "common-stuff"
> >> 
> >> DEPENDS_machine-1 = "${DEPENDS} this-stuff"
> > 
> > Yes, that will work. If the DEPENDS change implies some different
> > configuration I'd recommend being explicit about it as well e.g. via
> > EXTRA_OECONF or whatever is appropriate; this is particularly important
> > for the case where the extra dependency is not included and the configure
> > script for the application would auto-detect the presence of the
> > additional dependency in the absence of an explicit configure option.
> 
> Thanks. Is there some documentation that explains how the suffixes are build
> up, when they are used, etc. ?

These "suffixes" are called overrides in BitBake parlance. If an override 
appears in the OVERRIDES variable then it is applied, and the OVERRIDES 
variable is built up out of the values of various other variables (including 
MACHINE, DISTRO, etc - see 'bitbake -e | grep OVERRIDES'). I'm pretty sure 
this is covered in the BitBake manual, although unfortunately that is only 
available in source format right now.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre