<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 25 March 2017 at 17:34, Peter Kjellerstedt <span dir="ltr"><<a href="mailto:peter.kjellerstedt@axis.com" target="_blank">peter.kjellerstedt@axis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">> -----Original Message-----<br>
> From: <a href="mailto:openembedded-core-bounces@lists.openembedded.org">openembedded-core-bounces@<wbr>lists.openembedded.org</a><br>
> [mailto:<a href="mailto:openembedded-core-bounces@lists.openembedded.org">openembedded-core-<wbr>bounces@lists.openembedded.org</a><wbr>] On Behalf Of<br>
> Richard Purdie<br>
</span><span class="gmail-">> Sent: den 25 mars 2017 11:27<br>
> To: Peter Kjellerstedt; Andre McCurdy; OE Core mailing list<br>
> Subject: Re: [OE-core] Using MACHINE_FEATURES in a native recipe<br>
><br>
</span><span class="gmail-">> On Fri, 2017-03-24 at 15:10 +0000, Peter Kjellerstedt wrote:<br>
> > Even though I agree this is a good change and that it should be done,<br>
> > I wonder if we can either hold it off until after Pyro has been<br>
> > released or make it possible to avoid it? The reason for this is that<br>
> > I know that this change will require a huge amount of development<br>
> > work for us, something that will not be possible to do in the time<br>
> > frame left until Pyro is released. Or alternatively we will have to<br>
> > copy native.bbclass to our layers and maintain a fork of it, which<br>
> > sucks...<br>
> ><br>
> > The reason for this is that our unit test framework is based on<br>
> > building all our own packages as native, but still configured via,<br>
> > amongst others, MACHINE_FEATURES as if building for the real target.<br>
> > This will of course not work anymore if MACHINE_FEATURES is set to ""<br>
> > with no way of overriding it.<br>
><br>
> I'm afraid I only saw this after I merged it :(<br>
<br>
</span>No worries. I'll backport native.bbclass to our layers for now.<br>
<span class="gmail-"><br>
> I appreciate its a pain but I do think the change is the right thing to<br>
> do (maybe with a corresponding DISTRO_FEATURES one too). Hopefully we<br>
> can find a way that lets you work around it somehow...<br>
<br>
</span>I agree that cleaning MACHINE_FEATURES is the right thing to do. However,<br>
I am not so sure about DISTRO_FEATURES. After all, the native tools are<br>
part of the distro as well and there may be reasons to build them<br>
differently based on enabled features in the distro.<br></blockquote><div><br></div><div>It's possible but I've not found a single reason yet... If someone has a hunch about a distro feature actually affecting a native tool, please mention in <a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=11239">https://bugzilla.yoctoproject.org/show_bug.cgi?id=11239</a> </div><div> </div><div>Jussi</div></div></div></div>