> -----Original Message-----
> From: Eric Bénard [mailto:[email protected]]
> Sent: יום ה 11 אפריל 2013 15:53
> To: Michael Fainstein
> Cc: [email protected]
> Subject: Re: [yocto] how to use native executable from one recipe during
> install in another recipe
>
> Hi Michael,
>
> Le Thu, 11 Apr 2013 11:58:50 +0000,
> Michael Fainstein <[email protected]> a écrit :
> > I have one recipe that inherits "native", builds native executable and
> installs it in tmp/work/x86_64-linux/foo-native-1.00-r0/image/sbin/foo
> >
> do you have BBCLASSEXTEND = "native" in this recipe ?
>
> In the end, isn't the native binary installed in :
> sysroots/x86_64-linux/usr/sbin/ ?
>
> > Another recipe depends on first one and needs to execute foo in its
> do_install in order to install files in tmp/work/ppce500v2-fsl-linux-
> gnuspe/foo-1.00-r0/image/etc/
> >
> > I can't find a way to do it. Any suggestions? How can I install foo in
> first recipe to some common location that 2nd recipe can use? Is there such
> standard location?
> >
> You should then be able to call it in the other recipe as IIRC this path
> is in $PATH (and your recipe should depend on foo-native)
>
> Eric
Thanks!
I had a problem with do_populate_sysroot in native recipe due to bad generated
path for do_populate_sysroot[sstate-inputdirs]. I overrode it in my recipe with
do_populate_sysroot[sstate-inputdirs] = "${SYSROOT_DESTDIR}" and this recipe
was build successfully. However, foo was not installed in
sysroots/x86_64-linux.
I changed DESTDIR in 'make install' from ${D} to ${SYSROOT_DESTDIR} and finally
got foo were I need it.
Thanks,
Michael
This e-mail message is intended for the recipient only and contains information
which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have
received this transmission in error, please inform us by e-mail, phone or fax,
and then delete the original and all copies thereof.
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
