From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/6] staging: Don't put ptest files into the sysroot
Date: Mon, 6 Feb 2017 15:52:10 +0000 [thread overview]
Message-ID: <1486396334-8039-2-git-send-email-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <1486396334-8039-1-git-send-email-richard.purdie@linuxfoundation.org>
This wastes space/time as the ptest files aren't going to be used in the
sysroot so add them to the blacklist.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/classes/staging.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass
index 93d31eb..b92bdaf 100644
--- a/meta/classes/staging.bbclass
+++ b/meta/classes/staging.bbclass
@@ -31,6 +31,7 @@ SYSROOT_DIRS_BLACKLIST = " \
${datadir}/applications \
${datadir}/fonts \
${datadir}/pixmaps \
+ ${libdir}/${PN}/ptest \
"
sysroot_stage_dir() {
--
2.7.4
next prev parent reply other threads:[~2017-02-06 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 15:52 [PATCH 1/6] glibc: Separate locale files to their own sstate task Richard Purdie
2017-02-06 15:52 ` Richard Purdie [this message]
2017-02-06 15:52 ` [PATCH 3/6] perl-native: Remove .packinfo file Richard Purdie
2017-02-06 19:26 ` Martin Jansa
2017-02-07 7:57 ` Richard Purdie
2017-02-06 19:51 ` Khem Raj
2017-02-06 15:52 ` [PATCH 4/6] staging: Add shared manifest support Richard Purdie
2017-02-06 15:52 ` [PATCH 5/6] staging: Improve file creation resiliance Richard Purdie
2017-02-06 15:52 ` [PATCH 6/6] staging: Add missing parameter to debug message 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=1486396334-8039-2-git-send-email-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.