<div dir="ltr"><div dir="ltr">I wasn't completely clear in my origin post. We actually do use the mc to specify different DISTRO and IMAGE features. But my point was that, for recipies which are not affected by a change in those features, couldn't such as recipe's workdir be leveraged by another mc conf. But Richard's response was clear. That's not something which is supported, currently.<input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"enableNoauth":false,"persistentProtection":false,"expandedWatermarking":false,"expires":false,"isManaged":false},"attachments":{},"compose-id":"5","compose-window":{"secure":false}}"></div><br><div class="gmail_quote" style=""><div dir="ltr" class="gmail_attr">On Mon, Jul 1, 2019 at 10:13 AM <a href="mailto:chris.laplante@agilent.com">chris.laplante@agilent.com</a> <<a href="mailto:chris.laplante@agilent.com">chris.laplante@agilent.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> We have need to generate 6 slighly different images, with different dedicated applications and use cases, but they're all destined for<br>
> the same hardware.<br>
> We have multiconfig set to build these 6 variants. Clearly, they'll all share a majority of underlying packages.<br>
> While the bitbake initialization takes a long time (with multiconfig), we were under the impression that it could save time during the<br>
> actual build process because it could have the potential to reuse packages already built from mc A for mc B if the inputs to the recipes<br>
> are unchanged (if same xxx_FEATURES, same arch, etc.).<br>
> <br>
> This was a guess on our part since we initially didn't assign different tmp directories for each conf. So, the <WORKDIR> didn't change<br>
> between mc builds. That actually was causing some issues until we realized that separate tmp dirs was recommended for them.<br>
> Since they all now have separate tmp dirs, they clearly are not going to share work dirs, so, now we're questioning our original<br>
> assumption about any build-time speed benefit.<br>
<br>
Have you considered whether you actually need multiconfig in this case? If the arch and distro features don't change, you should just be able to have multiple image recipes.<br>
<br>
Chris <br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span><div><div dir="ltr"><div><div>Alan Kozlay<br></div><div dir="ltr">VES Solutions, LLC<br><span>Alan Kozlay <alan.kozlay@ves.solutions></span><div>DESK 443-595-7734<br></div><div>CELL 443-752-0323</div></div></div></div></div></span></div></div></div></div></div>