[
https://issues.apache.org/jira/browse/ARROW-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney resolved ARROW-1537.
---------------------------------
Resolution: Fixed
Issue resolved by pull request 1100
[https://github.com/apache/arrow/pull/1100]
> [C++] Support building with full path install_name on macOS
> -----------------------------------------------------------
>
> Key: ARROW-1537
> URL: https://issues.apache.org/jira/browse/ARROW-1537
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Kouhei Sutou
> Assignee: Kouhei Sutou
> Priority: Minor
> Labels: pull-request-available
> Fix For: 0.8.0
>
>
> The current libarrow.dylib uses @rpath/libarrow.0.dylib for install_name. It
> works well when we can set DYLD_LIBRARY_PATH environment variable or
> libarrow.dylib is installed into the standard path such as /usr/local/lib/.
> There are some cases that we can't set DYLD_LIBRARY_PATH. For example, we
> can't set DYLD_LIBRARY_PATH when we use libarrow.0.dylib via a shell script.
> Because the recent macOS doesn't inherit DYLD_LIBRARY_PATH for security
> reason. It's caused as System Integration Protection (SIP). We need to use
> libarrow.0.dylib via a shell script when we build Arrow GLib's *.gir files.
> It means that we need to install Arrow C++ into the standard path for
> building Arrow GLib on macOS. If we install Arrow C++ into the non-standard
> path such as ~/local/, we can't build Arrow GLib.
> If we use full path for libarrow.dylib's install_name, we don't need to set
> DYLD_LIBRARY_PATH. It means that we can build Arrow GLib with Arrow C++
> installed into the non-standard path such as ~/local/.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
