Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libevdev: adjust host-python dependency
Date: Sun,  6 Apr 2014 13:36:26 +0200	[thread overview]
Message-ID: <1396784186-13541-1-git-send-email-s.martin49@gmail.com> (raw)

libevdev depends on host-python because of some of its build scripts.
These build scripts support python2 and python3.

When python3 is part of the target selection, then we can just use the
interpreter provided by the host-python3 package.

Fixes:
  http://autobuild.buildroot.net/results/dd0/dd04833b11a0ebb0193c861cb375b2112dd339d1/

Signed-off-by: Samuel Martin <s.martin49@gmail.com>
---
 package/libevdev/libevdev.mk | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/package/libevdev/libevdev.mk b/package/libevdev/libevdev.mk
index 3a02230..fdaceb5 100644
--- a/package/libevdev/libevdev.mk
+++ b/package/libevdev/libevdev.mk
@@ -15,7 +15,9 @@ LIBEVDEV_DEPENDENCIES = host-pkgconf
 # Needs Python to generate a header file
 # We can't rely on the system Python, since it may be too old
 # (missing argparse in python 2.6)
-LIBEVDEV_DEPENDENCIES += host-python
+# libevdev build scripts support both python2 and python3, so avoid unneeded
+# dependency on host-python.
+LIBEVDEV_DEPENDENCIES += $(if $(BR2_PACKAGE_PYTHON3),host-python3,host-python)
 
 # package source code coming from git, so it doesn't have generated
 # configure and Makefile.in
-- 
1.9.1

             reply	other threads:[~2014-04-06 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-06 11:36 Samuel Martin [this message]
2014-04-06 12:10 ` [Buildroot] [PATCH] libevdev: adjust host-python dependency Thomas Petazzoni

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=1396784186-13541-1-git-send-email-s.martin49@gmail.com \
    --to=s.martin49@gmail.com \
    --cc=buildroot@busybox.net \
    /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