Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Crowe <mac@mcrowe.com>
To: openembedded-core@lists.openembedded.org
Cc: Mike Crowe <mac@mcrowe.com>
Subject: [PATCH 2/6] libsolv: Rely on cmake.bbclass to put cmake package files in dev package
Date: Sat,  6 Jan 2018 20:08:59 +0000	[thread overview]
Message-ID: <20180106200903.7624-3-mac@mcrowe.com> (raw)
In-Reply-To: <20180106200903.7624-1-mac@mcrowe.com>

cmake.bbclass now ensures that ${datadir}/cmake ends up in the dev package,
so this recipe doesn't need to do so itself.

Signed-off-by: Mike Crowe <mac@mcrowe.com>
---
 meta/recipes-extended/libsolv/libsolv_0.6.29.bb | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta/recipes-extended/libsolv/libsolv_0.6.29.bb b/meta/recipes-extended/libsolv/libsolv_0.6.29.bb
index e216921ea4..78972e5fed 100644
--- a/meta/recipes-extended/libsolv/libsolv_0.6.29.bb
+++ b/meta/recipes-extended/libsolv/libsolv_0.6.29.bb
@@ -25,7 +25,6 @@ EXTRA_OECMAKE = "-DLIB=${baselib} -DMULTI_SEMANTICS=ON -DENABLE_RPMMD=ON -DENABL
 
 PACKAGES =+ "${PN}-tools ${PN}ext"
 
-FILES_${PN}-dev += "${datadir}/cmake/Modules/FindLibSolv.cmake"
 FILES_${PN}-tools = "${bindir}/*"
 FILES_${PN}ext = "${libdir}/${PN}ext.so.*"
 
-- 
2.11.0




  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 ` [PATCH 1/6] cmake: Always put cmake package " Mike Crowe
2018-01-06 20:08 ` Mike Crowe [this message]
2018-01-06 20:09 ` [PATCH 3/6] vulkan: Rely on cmake.bbclass to put cmake package files in dev package 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-3-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