Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 09/17] rapidjson: rely on cmake.bbclass to put cmake package files in dev package
Date: Thu, 17 May 2018 18:30:38 -0700	[thread overview]
Message-ID: <1526607046-8081-9-git-send-email-armccurdy@gmail.com> (raw)
In-Reply-To: <1526607046-8081-1-git-send-email-armccurdy@gmail.com>

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

Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
 meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb b/meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb
index 8ab35d2..069385d 100644
--- a/meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb
+++ b/meta-oe/recipes-devtools/rapidjson/rapidjson_git.bb
@@ -20,7 +20,6 @@ EXTRA_OECMAKE += "-DRAPIDJSON_BUILD_DOC=OFF -DRAPIDJSON_BUILD_TESTS=OFF -DRAPIDJ
 
 # RapidJSON is a header-only C++ library, so the main package will be empty.
 
-FILES_${PN}-dev += "${libdir}/cmake"
 RDEPENDS_${PN}-dev = ""
 
 BBCLASSEXTEND = "native nativesdk"
-- 
1.9.1



  parent reply	other threads:[~2018-05-18  1:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  1:30 [meta-oe][PATCH 01/17] libwebsockets: rely on cmake.bbclass to put cmake package files in dev package Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 02/17] openobex: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 03/17] rocksdb: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 04/17] capnproto: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 05/17] grpc: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 06/17] json-spirit: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 07/17] librcf: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 08/17] msgpack-c: " Andre McCurdy
2018-05-18  1:30 ` Andre McCurdy [this message]
2018-05-18  1:30 ` [meta-oe][PATCH 10/17] glm: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 11/17] openjpeg: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 12/17] ceres-solver: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 13/17] gflags: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 14/17] libftdi: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 15/17] libssh: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 16/17] libtinyxml2: " Andre McCurdy
2018-05-18  1:30 ` [meta-oe][PATCH 17/17] poco: " Andre McCurdy
2018-05-18  1:56 ` [meta-oe][PATCH 01/17] libwebsockets: " Khem Raj
2018-05-18 19:07   ` Andre McCurdy
2018-05-18 21:01     ` Khem Raj
2018-05-18 22:28       ` Andre McCurdy
2018-05-19  2:37         ` Trevor Woerner
2018-05-19  4:52           ` Khem Raj
2018-05-19 11:59             ` Peter Kjellerstedt
2018-05-19 19:35               ` Trevor Woerner
2018-05-20  8:23                 ` André Draszik
2018-05-21 18:10                 ` Andre McCurdy
2018-05-24 17:30                   ` Trevor Woerner

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=1526607046-8081-9-git-send-email-armccurdy@gmail.com \
    --to=armccurdy@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