Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCHv3 0/1] Use fixed DISTRO_FEATURES for native
Date: Tue, 11 Apr 2017 17:35:29 +0300	[thread overview]
Message-ID: <cover.1491920909.git.jussi.kukkonen@intel.com> (raw)

Avoid signifant native task churn when DISTRO_FEATURES is changed
by defining (almost) fixed DISTRO_FEATURES for native recipes.

Add DISTRO_FEATURES_FILTER_NATIVE and DISTRO_FEATURES_NATIVE to
limit the changes to DISTRO_FEATURES when building native recipes.


Changes since V3:
* Use both DISTRO_FEATURES_FILTER_NATIVE (from v2) and
  DISTRO_FEATURES_NATIVE (from v1): see commit message for details
* Do the same thing for nativesdk
* Remove the x11 patches and solve the problem by always adding
  x11 to DISTRO_FEATURES_NATIVE and DISTRO_FEATURES_NATIVESDK
  (so it's used even when target DISTRO_FEATURES does not have it)


Thanks,
  Jussi

The following changes since commit 0793c758b15e5007b4dd4b146987a0e74d6f6cba:

  Revert "staging: Fix sysroot problem with populate_sysroot dependencies on do_fetch" (2017-04-11 00:57:03 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib jku/native-distro-features
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/native-distro-features

Jussi Kukkonen (1):
  native/nativesdk: Use fixed DISTRO_FEATURES

 meta/classes/native.bbclass    | 14 ++++++++++----
 meta/classes/nativesdk.bbclass |  6 ++++++
 meta/conf/bitbake.conf         |  9 +++++++++
 3 files changed, 25 insertions(+), 4 deletions(-)

-- 
2.1.4



             reply	other threads:[~2017-04-11 14:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 14:35 Jussi Kukkonen [this message]
2017-04-11 14:35 ` [PATCHv3 1/1] native/nativesdk: Use fixed DISTRO_FEATURES Jussi Kukkonen
2017-04-11 15:32   ` Peter Kjellerstedt
2017-04-11 17:16     ` Richard Purdie
2017-04-11 18:06       ` Peter Kjellerstedt
2017-04-11 21:12         ` Richard Purdie

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=cover.1491920909.git.jussi.kukkonen@intel.com \
    --to=jussi.kukkonen@intel.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