Re: Machine specific sysroot issue

[Khem Raj <raj.khem@gmail.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/14/2011 12:50 PM, Paul Eggleton wrote:
> 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?

I think with shared state it should be able to reuse what was built
before. It does not share the target sysroot like oe.dev
as long as the .pro file is part of a package it should be able to stage
it into machine sysroot and use it without causing a recompile

> 
> Cheers, Paul
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5IRrYACgkQuwUzVZGdMxSvEQCfblKkiL3uZLnwyjI+Nhymj9zf
zRUAn1BjKeIcTkHXvTFzAr2M5G0UK8qd
=6zRI
-----END PGP SIGNATURE-----