All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferry Toth <ftoth@telfort.nl>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: [PATCH] libgpiod_1.2: add a dependency on python when building python bindings
Date: Mon, 7 Jan 2019 13:56:15 +0100	[thread overview]
Message-ID: <ecb15e5d-ec71-d425-e188-9c3b6fd6cd11@telfort.nl> (raw)

Commit ab54dd75 "libgpiod: Rrecommend python3 only for PN-python 
package" also removes the build dependency

on python3 however this results in fatal error: Python.h: No such file 
or directory #include <Python.h>

Signed-off-by: Ferry Toth <ftoth@exalondelft.nl>

---
meta-oe/recipes-support/libgpiod/libgpiod_1.2.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-oe/recipes-support/libgpiod/libgpiod_1.2.bb 
b/meta-oe/recipes-support/libgpiod/libgpiod_1.2.bb
index dd080ff9d..93165a0c2 100644
--- a/meta-oe/recipes-support/libgpiod/libgpiod_1.2.bb
+++ b/meta-oe/recipes-support/libgpiod/libgpiod_1.2.bb
@@ -7,7 +7,7 @@ SRC_URI[sha256sum] = 
"b6b9079c933f7c8524815437937dda6b795a16141bca202a9eec70ba58
PACKAGECONFIG[cxx] = "--enable-bindings-cxx,--disable-bindings-cxx"
-PACKAGECONFIG[python3] = 
"--enable-bindings-python,--disable-bindings-python,"
+PACKAGECONFIG[python3] = 
"--enable-bindings-python,--disable-bindings-python,python3"
inherit ${@bb.utils.contains('PACKAGECONFIG', 'python3', 
'python3native', '', d)}
PACKAGES =+ "${PN}-python"


             reply	other threads:[~2019-01-07 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 12:56 Ferry Toth [this message]
2019-01-07 13:03 ` ✗ patchtest: failure for libgpiod_1.2: add a dependency on python when building python bindings (rev2) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2019-01-07 11:09 [PATCH] libgpiod_1.2: add a dependency on python when building python bindings Ferry Toth

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=ecb15e5d-ec71-d425-e188-9c3b6fd6cd11@telfort.nl \
    --to=ftoth@telfort.nl \
    --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 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.