Re: setting of BBPATH differs between ref manual and actual layer.conf file

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

On Wednesday 21 March 2012 05:23:07 Gary Thomas wrote:
> Indeed it does matter, as does the order that these statements are processed
> (which I think is the order the layers are listed in bblayers.conf?) 

Correct - each layer's layer.conf will be read in the order the layers are 
listed in bblayers.conf. Since variables such as BBPATH are usually appended 
or prepended within layer.conf, you will get different final values depending on 
the order they are listed.

> It can matter if two layers contain the same .conf file [at least].  I
> experienced this when I had two layers with abi_version.conf - actually
> three: meta, meta-yocto and meta-MINE - and I got very confused when I
> removed meta-yocto from the mix :-(  

I have to say, IMHO it is best practice to not expect to be able to change 
your layer configuration and keep the same previously-built TMPDIR contents. 
Now that we've enabled OEBasicHash (in Poky) that will protect you against 
most changes that could result from playing around with your layer config by 
forcing a rebuild of the affected recipes, but if you don't have that enabled 
it's entirely possible the contents of your TMPDIR (sysroots, output packages, 
etc.) will no longer match up with the metadata.

> The ordering of BBPATH isn't as important with recipes as they use the layer
> priority mechanism, but if you had two layers with identical priorities and
> recipes, it might matter as well.

BBPATH only influences how class, configuration and include files are found. It 
has no effect on searching for recipes themselves.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre