[
https://issues.apache.org/jira/browse/ARROW-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17661952#comment-17661952
]
Rok Mihevc commented on ARROW-4930:
-----------------------------------
This issue has been migrated to [issue
#21438|https://github.com/apache/arrow/issues/21438] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [Python] Remove LIBDIR assumptions in Python build
> --------------------------------------------------
>
> Key: ARROW-4930
> URL: https://issues.apache.org/jira/browse/ARROW-4930
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
> Affects Versions: 0.12.1
> Reporter: Suvayu Ali
> Assignee: Kouhei Sutou
> Priority: Minor
> Labels: pull-request-available, setup.py
> Fix For: 0.16.0
>
> Attachments: FindArrow.cmake.patch, FindParquet.cmake.patch
>
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> This is in reference to (4) in
> [this|http://mail-archives.apache.org/mod_mbox/arrow-dev/201903.mbox/%3C0AF328A1-ED2A-457F-B72D-3B49C8614850%40xhochy.com%3E]
> mailing list discussion.
> Certain sections of setup.py assume a specific location of the C++ libraries.
> Removing this hard assumption will simplify PyArrow builds significantly. As
> far as I could tell these assumptions are made in the
> {{build_ext._run_cmake()}} method (wherever bundling of C++ libraries are
> handled).
> # The first occurrence is before invoking cmake (see line 237).
> # The second occurrence is when the C++ libraries are moved from their build
> directory to the Python tree (see line 347). The actual implementation is in
> the function {{_move_shared_libs_unix(..)}} (see line 468).
> Hope this helps.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
