From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 5/6 v2] packagegroup-self-hosted: Use packagegroup-core-buildessential
Date: Tue, 12 Nov 2013 19:59:19 -0600 [thread overview]
Message-ID: <1384307965-10290-1-git-send-email-mark.hatle@windriver.com> (raw)
In-Reply-To: <cover.1384305535.git.mark.hatle@windriver.com>
Instead of manually specifying build dependencies, use the
packagegroup-core-buildessential. This ensures there is only one place
that needs to be modified when toolchain items and dependencies change.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
---
meta/recipes-core/packagegroups/packagegroup-self-hosted.bb | 12 +-----------
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb b/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
index 8e43201..e91a8d9 100644
--- a/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
+++ b/meta/recipes-core/packagegroups/packagegroup-self-hosted.bb
@@ -67,33 +67,23 @@ RRECOMMENDS_packagegroup-self-hosted-host-tools = "\
# eglibc-utils: for rpcgen
RDEPENDS_packagegroup-self-hosted-sdk = "\
- autoconf \
- automake \
- binutils \
ccache \
coreutils \
- cpp \
distcc \
eglibc-utils \
eglibc-gconv-ibm850 \
file \
findutils \
- g++ \
- gcc \
intltool \
ldd \
less \
libssp \
libssp-dev \
libssp-staticdev \
- libstdc++ \
- libstdc++-dev \
- libtool \
- make \
mktemp \
+ packagegroup-core-buildessential \
perl-module-re \
perl-module-text-wrap \
- pkgconfig \
quilt \
sed \
"
--
1.8.1.2.545.g2f19ada
next prev parent reply other threads:[~2013-11-13 1:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 1:23 [PATCH 0/6] Misc changes relating to toolchain and image gen Mark Hatle
2013-11-13 1:23 ` [PATCH 1/6] gcc: Use alternatives for the *-symlinks packages Mark Hatle
2013-11-13 2:24 ` Otavio Salvador
2013-11-13 2:27 ` Mark Hatle
2013-11-13 2:28 ` Otavio Salvador
2013-11-13 1:23 ` [PATCH 2/6] gcc: Drop *-symlinks Mark Hatle
2013-11-13 1:23 ` [PATCH 3/6] binutils: Ensure old -symlinks packages get removed Mark Hatle
2013-11-13 8:12 ` Martin Jansa
2013-11-13 11:14 ` Phil Blundell
2013-11-13 13:39 ` Mark Hatle
2013-11-13 13:44 ` Phil Blundell
2013-11-13 1:23 ` [PATCH 4/6] packagegroups: Remove toolchain *-symlinks packages Mark Hatle
2013-11-13 1:23 ` [PATCH 5/6] packagegroup-self-hosted: Use packagegroup-core-buildessentials Mark Hatle
2013-11-13 1:23 ` [PATCH 6/6] package_rpm: Allow translation of requirement to package name Mark Hatle
2013-11-13 1:33 ` [PATCH 0/6] Misc changes relating to toolchain and image gen Otavio Salvador
2013-11-13 2:01 ` Mark Hatle
2013-11-13 3:42 ` Mark Hatle
2013-11-13 1:59 ` Mark Hatle [this message]
2013-11-13 1:59 ` [PATCH 6/6 v2] package_rpm: Allow translation of requirement to package name Mark Hatle
2013-11-13 10:33 ` Paul Eggleton
2013-11-13 12:31 ` Otavio Salvador
2013-11-13 13:12 ` Mark Hatle
2013-11-15 14:02 ` Richard Purdie
2013-11-15 17:15 ` Mark Hatle
2013-11-13 14:19 ` [PATCH 2/6 v3] gcc: Drop *-symlinks Mark Hatle
2013-11-13 14:19 ` [PATCH 3/6 v3] binutils: Ensure old -symlinks packages get removed Mark Hatle
2013-11-19 0:40 ` [PATCH 0/6] Misc changes relating to toolchain and image gen Saul Wold
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=1384307965-10290-1-git-send-email-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