From: Mike Crowe <mac@mcrowe.com>
To: openembedded-core@lists.openembedded.org
Cc: Mike Crowe <mac@mcrowe.com>
Subject: [PATCH 1/6] cmake: Always put cmake package files in -dev packages
Date: Sat, 6 Jan 2018 20:08:58 +0000 [thread overview]
Message-ID: <20180106200903.7624-2-mac@mcrowe.com> (raw)
In-Reply-To: <20180106200903.7624-1-mac@mcrowe.com>
Various recipes that inherit cmake contain FILES_${PN}-dev magic to add the
generated package files to their -dev packages. Since this is a standard
feature of cmake, we might as well teach cmake.bbclass to do this itself so
those recipes can be simpler.
Signed-off-by: Mike Crowe <mac@mcrowe.com>
---
meta/classes/cmake.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
index ac2c1519b0..a4079dab0d 100644
--- a/meta/classes/cmake.bbclass
+++ b/meta/classes/cmake.bbclass
@@ -34,6 +34,8 @@ EXTRA_OECMAKE_append = " ${PACKAGECONFIG_CONFARGS}"
EXTRA_OECMAKE_BUILD_prepend_task-compile = "${PARALLEL_MAKE} "
EXTRA_OECMAKE_BUILD_prepend_task-install = "${PARALLEL_MAKEINST} "
+FILES_${PN}-dev += "${libdir}/cmake ${datadir}/cmake"
+
# CMake expects target architectures in the format of uname(2),
# which do not always match TARGET_ARCH, so all the necessary
# conversions should happen here.
--
2.11.0
next prev parent reply other threads:[~2018-01-06 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 20:08 [PATCH 0/6] Teach cmake.bbclass to put cmake page files in -dev packages Mike Crowe
2018-01-06 20:08 ` Mike Crowe [this message]
2018-01-06 20:08 ` [PATCH 2/6] libsolv: Rely on cmake.bbclass to put cmake package files in dev package Mike Crowe
2018-01-06 20:09 ` [PATCH 3/6] vulkan: " Mike Crowe
2018-01-06 20:09 ` [PATCH 4/6] waffle: " Mike Crowe
2018-01-06 20:09 ` [PATCH 5/6] libical: " Mike Crowe
2018-01-06 20:09 ` [PATCH 6/6] libproxy: " Mike Crowe
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=20180106200903.7624-2-mac@mcrowe.com \
--to=mac@mcrowe.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