<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hey Khem, Richard,<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 08/01/2018 10:44 AM, Khem Raj wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMKF1srz1dV8X-MP4si_DLd7esNpvynhSP_h-JOyK=mYABb35g@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div><br>
      </div>
      <div><br>
        <div class="gmail_quote">
          <div dir="ltr">On Tue, Jul 31, 2018 at 4:59 AM Richard Purdie
            &lt;<a href="mailto:richard.purdie@linuxfoundation.org"
              moz-do-not-send="true">richard.purdie@linuxfoundation.org</a>&gt;
            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>
            &gt; On 07/26/2018 08:36 PM, Khem Raj wrote:<br>
            &gt; &gt; <br>
            &gt; &gt; On 7/25/18 9:05 AM, Alejandro Enedino Hernandez
            Samaniego wrote:<br>
            &gt; &gt; &gt; This patch enables multiconfig dependencies
            (mcdepends) to be<br>
            &gt; &gt; &gt; used on<br>
            &gt; &gt; &gt; recipes using the following format:<br>
            &gt; &gt; &gt; <br>
            &gt; &gt; &gt; task[mcdepends] =
            "multiconfig:FROM-MC:TO-MC:PN:task-to-depend-<br>
            &gt; &gt; &gt; on"<br>
            &gt; &gt; &gt; <br>
            &gt; &gt; &gt; For the sake of simplicity consider the
            following example:<br>
            &gt; &gt; &gt; <br>
            &gt; &gt; &gt; Assuming we have set up multiconfig builds,
            one for qemux86 and<br>
            &gt; &gt; &gt; one for<br>
            &gt; &gt; &gt; qemuarm, named x86 and arm respectively.<br>
            &gt; &gt; &gt; <br>
            &gt; &gt; &gt; Adding the following line to an image recipe
            (core-image-sato):<br>
            &gt; &gt; &gt; do_image[mcdepends] =
            "multiconfig:x86:arm:core-image-<br>
            &gt; &gt; &gt; minimal:do_rootfs"<br>
            &gt; &gt; &gt; <br>
            &gt; &gt; <br>
            &gt; &gt; Do we really need to add multiconfig to keyword
            namespace ? can we<br>
            &gt; &gt; deduce this from "arch1:arch2:..."<br>
            &gt; <br>
            &gt; Bitbake already uses this and I believed adopting it
            would make it <br>
            &gt; easier for the user to understand its usage.<br>
            &gt;<br>
            &gt; For example, since the multiconfig names are also
            provided during<br>
            &gt; setup, if you assume that someone set up the build and
            a different<br>
            &gt; user is going through the recipe, arch1:arch2 wouldn't
            mean a lot for<br>
            &gt; 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 <br>
          </div>
        </div>
      </div>
    </blockquote>
    I also agree here that its better to use multiconfig.<br>
    <blockquote type="cite"
cite="mid:CAMKF1srz1dV8X-MP4si_DLd7esNpvynhSP_h-JOyK=mYABb35g@mail.gmail.com">
      <div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
            &gt; &gt; secondy, this need to be well documented, with
            examples for users<br>
            &gt; <br>
            &gt; I agree we could add more documentation to it, where do
            you think it <br>
            &gt; 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>
          </blockquote>
        </div>
      </div>
    </blockquote>
    Sure, I'll sync with Scott<br>
    <br>
    Thanks!,<br>
    <br>
    Alejandro<br>
    <blockquote type="cite"
cite="mid:CAMKF1srz1dV8X-MP4si_DLd7esNpvynhSP_h-JOyK=mYABb35g@mail.gmail.com">
      <div>
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            Its great to see this finally working!<br>
            <br>
            Cheers,<br>
            <br>
            Richard<br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>