From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH v3] Weston split out config recipe
Date: Thu, 25 Oct 2018 05:58:25 -0400 [thread overview]
Message-ID: <20181025095826.163943-1-mark.hatle@windriver.com> (raw)
Adding a cover page to explain the differences.
v3: Rename package from weston-cfg to weston-conf
Add missing SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
Add do_configure[noexec] to fix bitbake -c clean
v2: Add missing maintainer entry
v1: original
Mark Hatle (1):
weston: Split out machine specific configuration
meta/conf/distro/include/maintainers.inc | 1 +
meta/conf/layer.conf | 1 +
meta/recipes-graphics/wayland/weston-conf.bb | 35 +++++++++++++++++++++++++++
meta/recipes-graphics/wayland/weston_5.0.0.bb | 8 +-----
4 files changed, 38 insertions(+), 7 deletions(-)
create mode 100644 meta/recipes-graphics/wayland/weston-conf.bb
--
1.8.3.1
next reply other threads:[~2018-10-25 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 9:58 Mark Hatle [this message]
2018-10-25 9:58 ` [PATCH v3] weston: Split out machine specific configuration Mark Hatle
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=20181025095826.163943-1-mark.hatle@windriver.com \
--to=mark.hatle@windriver.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