Op 15 aug. 2011, om 16:42 heeft Paul Eggleton het volgende geschreven:
> On Monday 15 August 2011 15:30:53 Koen Kooi wrote:
>>> Same way it gets installed, it looks for it in ${OPIEDIR}. It's just that
>>> the second time around if the machine is not the same, ${OPIEDIR} is not
>>> the same either.
>>
>> That sounds like an expanded version is getting stored somewhere where it
>> shouldn't
>
> How could that be the case? If it stayed the same I could understand it...
>
> It's pretty straightforward; OPIEDIR is set to STAGING_DIR_HOST, but
> STAGING_DIR_HOST is now ${STAGING_DIR}/${MACHINE}, thus if you change the
> machine, STAGING_DIR_HOST also changes. In OE-dev (and Poky prior to machine-
> specific sysroots) STAGING_DIR_HOST was ${STAGING_DIR}/${BASEPKG_HOST_SYS},
> thus there was no problem.
if a recipe (or upstream code) does something like
echo $OPIEDIR > foo.config
And after you stage foo.config it will point to the old sysroot when changing
machine. In other words: something in opie isn't relocatable.
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
