All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegorslists@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/1] python-pylibftdi new package
Date: Tue, 28 Feb 2017 12:09:15 +0100	[thread overview]
Message-ID: <CAGm1_ks6jsEJepZCbM7iOR0GcG9LEdngPZjhNKP_JLgKfGck5Q@mail.gmail.com> (raw)
In-Reply-To: <1488201961-15539-1-git-send-email-christian.kellermann@solectrix.de>

Hi Christian,


On Mon, Feb 27, 2017 at 2:26 PM, Christian Kellermann
<christian.kellermann@solectrix.de> wrote:
> 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?

This is a known problem and so far there is no proper solution. So I
think the patch is acceptable.

Btw. have you tried libftdi's native Python support via SWIG?
pylibftdi hasn't reached version 1.0.0 and the project hasn't been
updated since September 2015.

Yegor

      parent reply	other threads:[~2017-02-28 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 13:26 [Buildroot] [PATCH 0/1] python-pylibftdi new package Christian Kellermann
2017-02-27 13:26 ` [Buildroot] [PATCH 1/1] libftdi: " 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 ` Yegor Yefremov [this message]

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=CAGm1_ks6jsEJepZCbM7iOR0GcG9LEdngPZjhNKP_JLgKfGck5Q@mail.gmail.com \
    --to=yegorslists@googlemail.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 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.