From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 9/9] python3-pycairo: update to 1.18.1
Date: Tue, 23 Apr 2019 18:19:16 +0200 [thread overview]
Message-ID: <20190423161916.25572-9-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20190423161916.25572-1-alex.kanavin@gmail.com>
Switch over to meson build, as it does not attempt to install
headers into /usr/share and pkg-config files into /usr/share/$libdir.
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
...3-pycairo_1.15.6.bb => python3-pycairo_1.18.1.bb} | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)
rename meta/recipes-devtools/python/{python3-pycairo_1.15.6.bb => python3-pycairo_1.18.1.bb} (65%)
diff --git a/meta/recipes-devtools/python/python3-pycairo_1.15.6.bb b/meta/recipes-devtools/python/python3-pycairo_1.18.1.bb
similarity index 65%
rename from meta/recipes-devtools/python/python3-pycairo_1.15.6.bb
rename to meta/recipes-devtools/python/python3-pycairo_1.18.1.bb
index 5c3e1e6f03b..db7cc921984 100644
--- a/meta/recipes-devtools/python/python3-pycairo_1.15.6.bb
+++ b/meta/recipes-devtools/python/python3-pycairo_1.18.1.bb
@@ -13,19 +13,15 @@ DEPENDS = "cairo"
SRC_URI = "https://github.com/pygobject/pycairo/releases/download/v${PV}/pycairo-${PV}.tar.gz"
UPSTREAM_CHECK_URI = "https://github.com/pygobject/pycairo/releases/"
-SRC_URI[md5sum] = "3ff210c34e7b052590e15fd0fb147766"
-SRC_URI[sha256sum] = "ad150ea637860836b66705e0513b8e59494538f0b80497ad3462051368755016"
+SRC_URI[md5sum] = "7610da8a40a7bed548991aa3416431d1"
+SRC_URI[sha256sum] = "70172e58b6bad7572a3518c26729b074acdde15e6fee6cbab6d3528ad552b786"
S = "${WORKDIR}/pycairo-${PV}"
-inherit setuptools3 pkgconfig
+inherit meson pkgconfig
CFLAGS += "-fPIC"
BBCLASSEXTEND = "native"
-do_install_append() {
- install -d ${D}${includedir}/pycairo/
- install -m 0644 ${D}${datadir}/include/pycairo/py3cairo.h ${D}${includedir}/pycairo/
-}
-FILES_${PN} += "${datadir}/include/pycairo/py3cairo.h"
+FILES_${PN} = "${PYTHON_SITEPACKAGES_DIR}/*"
--
2.17.1
next prev parent reply other threads:[~2019-04-23 16:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 16:19 [PATCH 1/9] msmtp: fix upstream version check Alexander Kanavin
2019-04-23 16:19 ` [PATCH 2/9] acpica: update to 20190405 Alexander Kanavin
2019-04-23 16:33 ` Burton, Ross
2019-04-23 16:50 ` Alexander Kanavin
2019-04-23 16:51 ` Burton, Ross
2019-04-23 16:19 ` [PATCH 3/9] gtk-doc.bbclass: unify option setting for meson-based recipes Alexander Kanavin
2019-04-24 6:50 ` Richard Purdie
2019-04-23 16:19 ` [PATCH 4/9] python-scons: update to 3.0.5 Alexander Kanavin
2019-04-23 16:19 ` [PATCH 5/9] python-setuptools: update to 41.0.1 Alexander Kanavin
2019-04-24 16:02 ` Richard Purdie
2019-04-24 16:20 ` Alexander Kanavin
2019-08-06 23:14 ` Paul Eggleton
2019-08-07 10:22 ` Alexander Kanavin
2019-08-07 10:49 ` Ross Burton
2019-04-23 16:19 ` [PATCH 6/9] python3-mako: update to 1.0.9 Alexander Kanavin
2019-04-23 16:19 ` [PATCH 7/9] python3-pbr: update to 5.1.3 Alexander Kanavin
2019-04-23 16:19 ` [PATCH 8/9] python3-pip: update to 19.0.3 Alexander Kanavin
2019-04-23 16:19 ` Alexander Kanavin [this message]
2019-04-24 15:49 ` [PATCH 9/9] python3-pycairo: update to 1.18.1 Richard Purdie
2019-04-24 16:30 ` Alexander Kanavin
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=20190423161916.25572-9-alex.kanavin@gmail.com \
--to=alex.kanavin@gmail.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