<div dir="ltr">Hi,<div><br></div><div>yes fw-utils is similar, but has different dependencies and builds slightly differently.</div><div><br></div><div>mkenvimage on the other hand is already built by current u-boot-mkimage recipe, just not installed by default (adding separate recipe would build it twice).</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 15, 2018 at 11:32 AM Alexey Brodkin <<a href="mailto:alexey.brodkin@synopsys.com">alexey.brodkin@synopsys.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Martin,<br>
<br>
On Thu, 2018-11-15 at 10:27 +0100, Martin Jansa wrote:<br>
> On Thu, Nov 15, 2018 at 05:15:03AM +0000, Alexey Brodkin wrote:<br>
> > Hi Marek,<br>
<br>
[snip]<br>
<br>
> > > Reviewed-by: Marek Vasut <<a href="mailto:marex@denx.de" target="_blank">marex@denx.de</a>><br>
> > > <br>
> > > That said, could the recipe for mkimage and mkenvimage be somehow<br>
> > > deduplicated ? There seems to be a lot of common stuff.<br>
> > <br>
> > I'd say why don't we just have one recipe for all U-Boot tools<br>
> > instead of adding tools one-by-one?<br>
> <br>
> Or add:<br>
> install -m 0755 tools/mkenvimage ${D}${bindir}/uboot-mkenvimage<br>
> ln -sf uboot-mkenvimage ${D}${bindir}/mkenvimage<br>
> <br>
> to existing u-boot-mkimage recipe, that's what I'm doing in<br>
> u-boot-mkimage bbappend.<br>
<br>
Sure and indeed that was my initial intention but then I noticed<br>
there're separate recipes for mkimage and fw-utils and decided<br>
to act similarly.<br>
<br>
If OE people is fine with addition of another (pretty similar ideologically)<br>
utility in <a href="http://u-boot-mkimage_xx.bb" rel="noreferrer" target="_blank">u-boot-mkimage_xx.bb</a> then I'm happy to implement it that way.<br>
<br>
-Alexey<br>
</blockquote></div>