overriding install in recipe for nativesdk

overriding install in recipe for nativesdk

[Marcin Krzemiński]

[-- Attachment #1: Type: text/plain, Size: 440 bytes --]

Hello,

Currently in our yocto layer there is a recipe for u-boot that also produce
mkimage binary for host,
I would like to have mkimage in SDK. Now, there is a separate recipe in
yocto to do that, but I am wondering is it possible in some way to override
install function for nativesdk. Then I could use same sources for u-boot
and I won't be downloading them twice.maybe there is another way that I can
try?

Regards,
Marcin

[-- Attachment #2: Type: text/html, Size: 522 bytes --]

Re: overriding install in recipe for nativesdk

[Khem Raj]

On Tue, Jul 14, 2015 at 9:57 PM, Marcin Krzemiński
<mar.krzeminski@gmail.com> wrote:
> Currently in our yocto layer there is a recipe for u-boot that also produce
> mkimage binary for host,
> I would like to have mkimage in SDK. Now, there is a separate recipe in
> yocto to do that, but I am wondering is it possible in some way to override
> install function for nativesdk. Then I could use same sources for u-boot and
> I won't be downloading them twice.maybe there is another way that I can try?

you could use shared-workdir model like what kernel and gcc use but
maintenance of such a setup is high
it may be appealing for components with large sourcecode and multiple
recipes uboot may not be particularly suitable

Re: overriding install in recipe for nativesdk

[mar.krzeminski]

Thanks for the clue, but as you mentioned u-boot is small so there is no 
big problem with that.

W dniu 13.08.2015 o 19:36, Khem Raj pisze:
> On Tue, Jul 14, 2015 at 9:57 PM, Marcin Krzemiński
> <mar.krzeminski@gmail.com> wrote:
>> Currently in our yocto layer there is a recipe for u-boot that also produce
>> mkimage binary for host,
>> I would like to have mkimage in SDK. Now, there is a separate recipe in
>> yocto to do that, but I am wondering is it possible in some way to override
>> install function for nativesdk. Then I could use same sources for u-boot and
>> I won't be downloading them twice.maybe there is another way that I can try?
> you could use shared-workdir model like what kernel and gcc use but
> maintenance of such a setup is high clue
> it may be appealing for components with large sourcecode and multiple
> recipes uboot may not be particularly suitable
>