From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] Use fixed DISTRO_FEATURES for native
Date: Fri, 07 Apr 2017 22:47:36 +0100 [thread overview]
Message-ID: <1491601656.17200.104.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1491483222.git.jussi.kukkonen@intel.com>
On Fri, 2017-04-07 at 09:08 +0300, Jussi Kukkonen wrote:
> Avoid signifant native task churn when DISTRO_FEATURES is changed
> by defining a fixed DISTRO_FEATURES value (default is "") for native
> recipes.
>
> The xorg changes are all removals of x11 requirements (that were not
> real) from recipes that have native versions.
>
> I added a configuration default in bitbake.conf, let me know if this
> is not a good place.
>
> This seems to work fine (tested multiple different images) but I am
> not really sure how to test it further... Suggestions are welcome, as
> are results from autobuilder.
Close, but:
https://autobuilder.yocto.io/builders/nightly-no-x11/builds/225/steps/BuildImages/logs/stdio
:/
Cheers,
Richard
next prev parent reply other threads:[~2017-04-07 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 6:08 [PATCH 0/4] Use fixed DISTRO_FEATURES for native Jussi Kukkonen
2017-04-07 6:09 ` [PATCH 1/4] mkfontdir: Remove x11 requirement Jussi Kukkonen
2017-04-07 6:09 ` [PATCH 2/4] mkfontscale: " Jussi Kukkonen
2017-04-07 6:09 ` [PATCH 3/4] xorg-font-common.inc: " Jussi Kukkonen
2017-04-07 6:09 ` [PATCH 4/4] native.bbclass: Use fixed DISTRO_FEATURES Jussi Kukkonen
2017-04-07 8:28 ` Richard Purdie
2017-04-07 11:59 ` Jussi Kukkonen
2017-04-07 12:13 ` Richard Purdie
2017-04-07 13:06 ` Jussi Kukkonen
2017-04-07 21:47 ` Richard Purdie [this message]
2017-04-08 7:26 ` [PATCH 0/4] Use fixed DISTRO_FEATURES for native 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=1491601656.17200.104.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=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