All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][master-next][PATCH v3 14/17] libtinyxml2: rely on cmake.bbclass to put cmake package files in dev package
Date: Thu, 24 May 2018 10:38:51 -0400	[thread overview]
Message-ID: <20180524143854.24096-15-twoerner@gmail.com> (raw)
In-Reply-To: <20180524143854.24096-1-twoerner@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

Originally-conceived-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
---
 meta-oe/recipes-support/libtinyxml2/libtinyxml2_5.0.1.bb | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta-oe/recipes-support/libtinyxml2/libtinyxml2_5.0.1.bb b/meta-oe/recipes-support/libtinyxml2/libtinyxml2_5.0.1.bb
index 8b5ab44fdd..c763a6c2b3 100644
--- a/meta-oe/recipes-support/libtinyxml2/libtinyxml2_5.0.1.bb
+++ b/meta-oe/recipes-support/libtinyxml2/libtinyxml2_5.0.1.bb
@@ -12,6 +12,4 @@ S = "${WORKDIR}/git"
 
 inherit cmake
 
-FILES_${PN}-dev += "${libdir}/cmake/"
-
 BBCLASSEXTEND = "native"
-- 
2.17.0.582.gccdcbd54c



  parent reply	other threads:[~2018-05-24 14:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 14:38 [meta-oe][master-next][PATCH v3 00/17] rely on cmake.bbclass to put cmake package files in dev package Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 01/17] openobex: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 02/17] rocksdb: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 03/17] capnproto: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 04/17] json-spirit: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 05/17] librcf: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 06/17] msgpack_c: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 07/17] rapidjson: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 08/17] glm: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 09/17] openjpeg: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 10/17] ceres-solver: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 11/17] gflags: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 12/17] libftdi: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 13/17] libssh: " Trevor Woerner
2018-05-24 14:38 ` Trevor Woerner [this message]
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 15/17] libwebsockets: " Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 16/17] opencv: " Trevor Woerner
2018-05-25  3:19   ` Anuj Mittal
2018-05-25 15:08     ` Trevor Woerner
2018-05-24 14:38 ` [meta-oe][master-next][PATCH v3 17/17] libeigen: " Trevor Woerner
2018-05-25 15:22   ` Trevor Woerner
2018-05-25 19:58     ` Andre McCurdy
2018-05-26  2:45       ` Trevor Woerner
2018-05-26  2:49         ` Trevor Woerner
2018-05-29 19:55           ` Khem Raj

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=20180524143854.24096-15-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 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.