[
https://issues.apache.org/jira/browse/ARROW-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093185#comment-17093185
]
Remi Dettai commented on ARROW-8565:
------------------------------------
I finally managed to make a static build but it requires changing the root
CMakeLists to append AWSSDK_LINK_LIBRARIES to ARROW_STATIC_LINK_LIBS. I'm not
sure this is safe to do because I really don't understand how the Arrow and AWS
SDK dependencies are competing.
In the end the static build is barely more compact than the shared one, because
the C++ AWS SDK build is a whole adventure. I'm continuing my investigation to
see if I can come up with something nicer, but I really lack some cmake
expertise :)
> [C++] Static build with AWS SDK
> -------------------------------
>
> Key: ARROW-8565
> URL: https://issues.apache.org/jira/browse/ARROW-8565
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 0.17.0
> Reporter: Remi Dettai
> Priority: Major
> Labels: aws-s3, build-problem
>
> I can't find my way around the build system when using the S3 client.
> It seems that only shared target is allowed when the S3 feature is ON. In the
> thirdparty toolchain, when printing:
> ??FATAL_ERROR "FIXME: Building AWS C++ SDK from source will link with wrong
> libcrypto"??
> What is actually meant is that static build will not work, correct ? If it is
> the case, should libarrow.a be generated at all when S3 feature is on ?
> What can be done to fix this ? What does it mean that the SDK links to the
> wrong libcrypto ? Is it fixable ? Or is their a way to have the static build
> but maintain a dynamic link to a shared version of the SDK ?
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
