mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] how to integrate python modules using find_library
Date: Fri, 8 Nov 2019 18:45:54 +0100	[thread overview]
Message-ID: <20191108174554.aeqmq6og5doibrmo@pengutronix.de> (raw)
In-Reply-To: <CABDcavZFPk+OrDFosRXsq_eMbHX7PjOmVUCe5qYwnpALcf2BRQ@mail.gmail.com>

On Tue, Nov 05, 2019 at 06:11:27PM +0100, Guillermo Rodriguez Garcia wrote:
> Some python packages (e.g. soundfile) rely on find_library (from
> ctypes.util) to resolve the name of a dynamic library at runtime in a
> platform-independent way.
> 
> On Linux, the implementation of find_library [1] requires one of the
> following:
>  - ldconfig
>  - gcc + objdump
>  - ld + objdump
> 
> Neither of the above make much sense on an embedded target. Does anyone
> have advice or recommendations on how to deal with such packages, short of
> just patching the sources to avoid the use of find_library?
> 
>  [1]:
> https://github.com/python/cpython/blob/e42b705188271da108de42b55d9344642170aa2b/Lib/ctypes/util.py#L309

Well, ldconfig should be useable. PTXdist optionally installs it to
generate the ld.so.cache, but it's quite large because it must be
statically linked.
I've no idea what else to use.

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2019-11-08 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 17:11 Guillermo Rodriguez Garcia
2019-11-08 17:45 ` Michael Olbrich [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=20191108174554.aeqmq6og5doibrmo@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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