You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Will Jones (Jira)" <ji...@apache.org> on 2022/08/09 14:59:00 UTC
[jira] [Closed] (ARROW-17295) [C++] Build separate bundled_depenencies.so
[ https://issues.apache.org/jira/browse/ARROW-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Will Jones closed ARROW-17295.
------------------------------
Resolution: Won't Fix
> [C++] Build separate bundled_depenencies.so
> -------------------------------------------
>
> Key: ARROW-17295
> URL: https://issues.apache.org/jira/browse/ARROW-17295
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 8.0.0, 8.0.1
> Reporter: Will Jones
> Priority: Major
>
> When building arrow _static_ libraries with bundled dependencies, we produce {{{}arrow_bundled_dependencies.a{}}}. But when building dynamic libraries, the bundled dependencies are statically linked directly into the arrow libraries (libarrow, libarrow_flight, etc.). This means that users can access the symbols of bundled dependencies in the static case, but not in the dynamic library case.
> One use case of this is being able to pass in gRPC configuration to a Flight server, which requires access to gRPC symbols.
> Could we change the dynamic library building to build an {{arrow_bundled_dependencies.so}} so that the symbols are accessible?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)