On Tue, Jun 17, 2014 at 10:11 PM, Brian Smucker wrote:
> Hi Andrea and all,
>
> So I am using your suggestion to make another variant of busybox:
> busybox-static, and I add the static.bblcass file.
>
> So when I try to do bitbake busybox-static, it ends up unpacking to
> busybox-static-1.20.2-r2/
Hi Andrea and all,
So I am using your suggestion to make another variant of busybox:
busybox-static, and I add the static.bblcass file.
So when I try to do bitbake busybox-static, it ends up unpacking to
busybox-static-1.20.2-r2/busybox-1.20.2 (which does not correspond to
the S variable).
A
Andrea,
Thanks for your reply.
In my case, the difference in the two recipes is quite minimal: a
different defconfig and a modified busybox.inc.
Generating the altered recipe is not my question.
My question is, now that I have two overlayed recipes for busybox, the
standard and the custom,
On Tue, Jun 17, 2014 at 5:41 PM, Brian Smucker wrote:
> Hello,
>
> I would like to have yocto generate two copies of busybox, one
> statically-linked and one dynamically linked. So I try to make a copy of the
> busybox recipe and give it a new name like busybox-s_x.bb
>
> But my knowlege of yo
Hello,
I would like to have yocto generate two copies of busybox, one
statically-linked and one dynamically linked. So I try to make a copy of
the busybox recipe and give it a new name like busybox-s_x.bb
But my knowlege of yocto comes up short and I get lots of errors.
Is there a way to