From: "Andreas Müller" <schnitzeltony@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [PATCH 16/17] libeigen: upgrade 3.3.7 -> 3.3.7
Date: Sat, 22 May 2021 03:35:20 +0200 [thread overview]
Message-ID: <20210522013521.588774-16-schnitzeltony@gmail.com> (raw)
In-Reply-To: <20210522013521.588774-1-schnitzeltony@gmail.com>
Simplify packaging a bit
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
---
.../libeigen/{libeigen_3.3.7.bb => libeigen_3.3.9.bb} | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
rename meta-oe/recipes-support/libeigen/{libeigen_3.3.7.bb => libeigen_3.3.9.bb} (77%)
diff --git a/meta-oe/recipes-support/libeigen/libeigen_3.3.7.bb b/meta-oe/recipes-support/libeigen/libeigen_3.3.9.bb
similarity index 77%
rename from meta-oe/recipes-support/libeigen/libeigen_3.3.7.bb
rename to meta-oe/recipes-support/libeigen/libeigen_3.3.9.bb
index 6ce318d0b..d6ef98f94 100644
--- a/meta-oe/recipes-support/libeigen/libeigen_3.3.7.bb
+++ b/meta-oe/recipes-support/libeigen/libeigen_3.3.9.bb
@@ -6,14 +6,13 @@ LIC_FILES_CHKSUM = "file://COPYING.MPL2;md5=815ca599c9df247a0c7f619bab123dad"
SRC_URI = "git://gitlab.com/libeigen/eigen.git;protocol=http;nobranch=1"
-SRCREV = "21ae2afd4edaa1b69782c67a54182d34efe43f9c"
+SRCREV = "0fd6b4f71dd85b2009ee4d1aeb296e2c11fc9d68"
S = "${WORKDIR}/git"
inherit cmake
-FILES_${PN} = "${libdir}"
-FILES_${PN}-dev = "${includedir} ${datadir}/eigen3/cmake ${datadir}/cmake/Modules ${datadir}/pkgconfig"
+FILES_${PN}-dev += "${datadir}/eigen3/cmake"
# ${PN} is empty so we need to tweak -dev and -dbg package dependencies
RDEPENDS_${PN}-dev = ""
--
2.31.1
next prev parent reply other threads:[~2021-05-22 1:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 1:35 [PATCH 01/17] giflib: upgrade 5.1.4 -> 5.2.1 Andreas Müller
2021-05-22 1:35 ` [PATCH 02/17] gnuplot: upgrade 5.2.8 -> 5.4.1 Andreas Müller
2021-05-22 1:35 ` [PATCH 03/17] zsh: upgrade 5.4.2 -> 5.8 Andreas Müller
2021-05-22 1:35 ` [PATCH 04/17] ttf-lohit: upgrade 2 -> 2.92.1 Andreas Müller
2021-05-22 1:35 ` [PATCH 05/17] xrdp: upgrade 0.9.15 -> 0.9.16 Andreas Müller
2021-05-22 1:35 ` [PATCH 06/17] snappy: upgrade 1.1.8 -> 1.1.9 Andreas Müller
2021-05-22 1:35 ` [PATCH 07/17] redis: upgrade 6.2.2 -> 6.2.3 Andreas Müller
2021-05-22 1:35 ` [PATCH 08/17] remmina: upgrade 1.4.11 -> 1.4.17 Andreas Müller
2021-05-22 1:35 ` [PATCH 09/17] libpeas: upgrade 1.26.0 -> 1.30.0 Andreas Müller
2021-05-22 1:35 ` [PATCH 10/17] modemmanager: upgrade 1.16.2 -> 1.16.4 Andreas Müller
2021-05-22 1:35 ` [PATCH 11/17] mm-common: upgrade 1.0.2 -> 1.0.3 Andreas Müller
2021-05-22 1:35 ` [PATCH 12/17] protobuf: upgrade 3.15.2 -> 3.17.0 Andreas Müller
2021-05-22 1:35 ` [PATCH 13/17] protobuf-c: upgrade 1.3.3 -> 1.4.0 Andreas Müller
2021-05-22 12:44 ` [oe] " Khem Raj
2021-05-22 15:15 ` Andreas Müller
2021-05-22 1:35 ` [PATCH 14/17] qpdf: upgrade 10.2.0 -> 10.3.2 Andreas Müller
2021-05-22 1:35 ` [PATCH 15/17] libmxml: upgrade 3.1 -> 3.2 Andreas Müller
2021-05-22 1:35 ` Andreas Müller [this message]
2021-05-22 8:36 ` [oe] [PATCH 16/17] libeigen: upgrade 3.3.7 -> 3.3.7 Jose Quaresma
2021-05-22 9:10 ` Andreas Müller
2021-05-22 1:35 ` [PATCH 17/17] libgusb: upgrade 0.3.5 -> 0.3.6 Andreas Müller
2021-05-22 2:59 ` [oe] [PATCH 01/17] giflib: upgrade 5.1.4 -> 5.2.1 Khem Raj
2021-05-22 8:28 ` Andreas Müller
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=20210522013521.588774-16-schnitzeltony@gmail.com \
--to=schnitzeltony@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.