[
https://issues.apache.org/jira/browse/ARROW-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874905#comment-15874905
]
Uwe L. Korn commented on ARROW-566:
-----------------------------------
{{libarrow*}} and {{libparquet*}} are dynamically linked currently in the
wheels. The correct {{RPATH}} is set via {{auditwheel}} but also a hash is
appended at the end of the libname so that different wheels can have different
versions of the same library. As {{pyarrow}} is the main authority for
{{libarrow}} in a pip-based setup, there should be no need for the hash-based
suffix. The main things to tackle in this issue are:
* Set the correct RPATHs in {{libpyarrow}} and {{libparquet_arrow}}
* Bundle the above shared libraries in {{pyarrow}}.
My main intention is to build {{turbodbc}} wheels based upon {{pyarrow}} wheels
but this should also be needed for any python package consuming both the C++
and Python API of Arrow.
> Python: Deterministic position of libarrow in manylinux1 wheels
> ---------------------------------------------------------------
>
> Key: ARROW-566
> URL: https://issues.apache.org/jira/browse/ARROW-566
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
> Reporter: Uwe L. Korn
> Assignee: Uwe L. Korn
>
> To link other Python wheels to the {{pyarrow}}, the position and name of all
> shared libraries should be deterministic. Currently using {{libarrow}} in
> other Python packages is only possible using the conda packaging stack, via
> pip installable paths.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
