[
https://issues.apache.org/jira/browse/ARROW-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575258#comment-17575258
]
David Li commented on ARROW-17295:
----------------------------------
There's a 'last resort' escape hatch, but you must take care of linking to the
exact same version of gRPC as used by Arrow:
https://github.com/apache/arrow/blob/master/cpp/examples/arrow/flight_grpc_example.cc
> [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)
