From: Christian Kellermann <christian.kellermann@solectrix.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/1] python-pylibftdi new package
Date: Mon, 27 Feb 2017 14:26:00 +0100 [thread overview]
Message-ID: <1488201961-15539-1-git-send-email-christian.kellermann@solectrix.de> (raw)
Dear List,
This patch adds the python binding for libftdi. However it contains a
hackish patch which I would like to discuss. Pylibftdi uses the ctypes
find_library call to find the libusb and libftdi libraries. This in
turn seems to rely on ldconfig which is not part of buildroot.
Patching it out here seems to work fine, but this kind of hides the
general problem of fixing find_library in the python package. How
would one do this properly?
Thanks,
Christian
Christian Kellermann (1):
libftdi: new package
package/Config.in | 1 +
.../python-pylibftdi/0001-do-not-use-find-library.patch | 14 ++++++++++++++
package/python-pylibftdi/Config.in | 13 +++++++++++++
package/python-pylibftdi/python-libftdi.hash | 3 +++
package/python-pylibftdi/python-libftdi.mk | 15 +++++++++++++++
5 files changed, 46 insertions(+)
create mode 100644 package/python-pylibftdi/0001-do-not-use-find-library.patch
create mode 100644 package/python-pylibftdi/Config.in
create mode 100644 package/python-pylibftdi/python-libftdi.hash
create mode 100644 package/python-pylibftdi/python-libftdi.mk
--
2.1.4
next reply other threads:[~2017-02-27 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 13:26 Christian Kellermann [this message]
2017-02-27 13:26 ` [Buildroot] [PATCH 1/1] libftdi: new package Christian Kellermann
2017-02-28 11:04 ` Yegor Yefremov
2017-03-01 13:03 ` [Buildroot] [PATCH v2] python-pylibftdi: " Christian Kellermann
2017-03-01 14:34 ` Thomas Petazzoni
2017-03-01 16:18 ` [Buildroot] [PATCH v3 1/1] " Christian Kellermann
2017-03-02 8:29 ` Yegor Yefremov
2017-03-05 20:38 ` Thomas Petazzoni
2017-03-06 8:20 ` Thomas Petazzoni
2017-03-06 17:11 ` Yann E. MORIN
2017-02-28 11:09 ` [Buildroot] [PATCH 0/1] python-pylibftdi " Yegor Yefremov
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=1488201961-15539-1-git-send-email-christian.kellermann@solectrix.de \
--to=christian.kellermann@solectrix.de \
--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 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.