From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-networking][master-next][PATCH 1/2] rely on cmake.bbclass to put cmake package files in dev package
Date: Sat, 19 May 2018 22:40:25 -0400 [thread overview]
Message-ID: <20180520024025.10446-1-twoerner@gmail.com> (raw)
The cmake.bbclass in oe-core now ensures that ${libdir}/cmake and
${datadir}/cmake end up in the dev package, so recipes no longer need to
provide custom packaging rules to handles these files.
http://git.openembedded.org/openembedded-core/commit/?id=d91dc4666683a96e9d03cbbd21b8a546f9069c93
Originally-conceived-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
meta-networking/recipes-devtools/grpc/grpc_1.8.5.bb | 2 --
meta-networking/recipes-support/c-ares/c-ares_1.13.0.bb | 1 -
2 files changed, 3 deletions(-)
diff --git a/meta-networking/recipes-devtools/grpc/grpc_1.8.5.bb b/meta-networking/recipes-devtools/grpc/grpc_1.8.5.bb
index 0883ec176b..e9491c45a9 100644
--- a/meta-networking/recipes-devtools/grpc/grpc_1.8.5.bb
+++ b/meta-networking/recipes-devtools/grpc/grpc_1.8.5.bb
@@ -31,6 +31,4 @@ EXTRA_OECMAKE = " \
-DBUILD_SHARED_LIBS=ON \
"
-FILES_${PN}-dev += "${libdir}/cmake"
-
BBCLASSEXTEND = "native"
diff --git a/meta-networking/recipes-support/c-ares/c-ares_1.13.0.bb b/meta-networking/recipes-support/c-ares/c-ares_1.13.0.bb
index 70e497f5f0..defbeaa623 100644
--- a/meta-networking/recipes-support/c-ares/c-ares_1.13.0.bb
+++ b/meta-networking/recipes-support/c-ares/c-ares_1.13.0.bb
@@ -18,7 +18,6 @@ inherit cmake pkgconfig
PACKAGES =+ "${PN}-utils"
-FILES_${PN}-dev += "${libdir}/cmake"
FILES_${PN}-utils = "${bindir}"
BBCLASSEXTEND = "native"
--
2.17.0.582.gccdcbd54c
reply other threads:[~2018-05-20 2:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180520024025.10446-1-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=openembedded-devel@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