Machine specific sysroot issue

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

Hi all,

I've brought over the Opie recipes from OE in preparation for creating a 
separate layer, and after making a few changes everything compiles OK; however 
I'm finding that the change to machine-specific sysroots is causing some 
problems.

libopie2, a non-machine specific package, among other things installs a file 
called include.pro into ${OPIEDIR}, which is configured to be 
${STAGING_DIR_HOST}. In OE-classic ${STAGING_DIR_HOST} is not machine-specific, 
so if you build libopie2 for machine A then build some other package that 
needs include.pro for machine B, then everything is fine. In the OE-core case 
with machine-specific sysroots it's looking for the file in the sysroot for the 
current machine, which if you've been building for several different machines 
may not be where it has actually been installed.

What's the correct way to fix this? Is libopie2 now installing this file in the 
wrong place?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre