<div><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jul 31, 2018 at 4:59 AM Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, 2018-07-30 at 15:05 -0700, Alejandro Enedino Hernandez<br>
Samaniego wrote:<br>
> On 07/26/2018 08:36 PM, Khem Raj wrote:<br>
> > <br>
> > On 7/25/18 9:05 AM, Alejandro Enedino Hernandez Samaniego wrote:<br>
> > > This patch enables multiconfig dependencies (mcdepends) to be<br>
> > > used on<br>
> > > recipes using the following format:<br>
> > > <br>
> > > task[mcdepends] = "multiconfig:FROM-MC:TO-MC:PN:task-to-depend-<br>
> > > on"<br>
> > > <br>
> > > For the sake of simplicity consider the following example:<br>
> > > <br>
> > > Assuming we have set up multiconfig builds, one for qemux86 and<br>
> > > one for<br>
> > > qemuarm, named x86 and arm respectively.<br>
> > > <br>
> > > Adding the following line to an image recipe (core-image-sato):<br>
> > > do_image[mcdepends] = "multiconfig:x86:arm:core-image-<br>
> > > minimal:do_rootfs"<br>
> > > <br>
> > <br>
> > Do we really need to add multiconfig to keyword namespace ? can we<br>
> > deduce this from "arch1:arch2:..."<br>
> <br>
> Bitbake already uses this and I believed adopting it would make it <br>
> easier for the user to understand its usage.<br>
><br>
> For example, since the multiconfig names are also provided during<br>
> setup, if you assume that someone set up the build and a different<br>
> user is going through the recipe, arch1:arch2 wouldn't mean a lot for<br>
> that user because they may not map 1:1 to MACHINE names.<br>
<br>
It is consistent with the rest of the system. I'm still torn on whether<br>
we should shorten "multiconfig:" to "mc:" but we need to be consistent.<br>
</blockquote><div dir="auto"><br></div><div dir="auto">Given a choice I would suggest for using multiconfig for lesser chance of conflicts </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> > secondy, this need to be well documented, with examples for users<br>
> <br>
> I agree we could add more documentation to it, where do you think it <br>
> should go?<br>
<br>
I'm going to queue the patches for testing in -next, they look good to<br>
me just reading the patches.<br>
<br>
Could you start to work with Scott (cc'd) to get this new dependency<br>
type listed in the bitbake manual and anywhere else it needs to be<br>
documented?<br>
<br>
Its great to see this finally working!<br>
<br>
Cheers,<br>
<br>
Richard<br>
<br>
</blockquote></div></div>