From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: Using MACHINE_FEATURES in a native recipe
Date: Thu, 23 Mar 2017 16:43:24 +0000 [thread overview]
Message-ID: <1490287404.13980.231.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=WhxRaQ42=2bsFVZpeLhrZo2XwZBYoWp=f42tyebo2=2A@mail.gmail.com>
On Wed, 2017-03-22 at 14:42 -0700, Andre McCurdy wrote:
> Currently native.bbclass clears MACHINEOVERRIDES but leaves
> MACHINE_FEATURES alone. Is that an oversight? Or is there ever a
> legitimate reason for a native recipe to have a dependency on
> MACHINE_FEATURES?
There is no good reason. Currently having this dilemma with
DISTRO_FEATURES too :/.
opkg-native rebuilding if you enable/disable systemd isn't
expected/nice.
Cheers,
Richard
next prev parent reply other threads:[~2017-03-23 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 21:42 Using MACHINE_FEATURES in a native recipe Andre McCurdy
2017-03-22 21:46 ` Khem Raj
2017-03-22 23:00 ` Andre McCurdy
2017-03-22 23:59 ` Khem Raj
2017-03-23 16:43 ` Richard Purdie [this message]
2017-03-24 15:10 ` Peter Kjellerstedt
2017-03-25 10:27 ` Richard Purdie
2017-03-25 15:34 ` Peter Kjellerstedt
2017-03-26 17:09 ` Jussi Kukkonen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1490287404.13980.231.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox