[jira] [Resolved] (ARROW-224) [C++] Address static linking of boost dependencies

["Wes McKinney (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARROW-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes McKinney resolved ARROW-224.
--------------------------------
    Resolution: Fixed
      Assignee: Wes McKinney

This was done some time ago in https://github.com/apache/arrow/commit/77598fa59a92c07dedf7d93307e5c72c5b2724d0

As an example, we are statically linking boost symbols in conda-forge builds: https://github.com/conda-forge/arrow-cpp-feedstock/blob/master/recipe/build.sh#L16

> [C++] Address static linking of boost dependencies
> --------------------------------------------------
>
>                 Key: ARROW-224
>                 URL: https://issues.apache.org/jira/browse/ARROW-224
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++
>            Reporter: Wes McKinney
>            Assignee: Wes McKinney
>
> As a follow up to ARROW-222, we will want to provide the option of standalone shared Arrow libraries, or at least forcing certain dependencies (like boost) to be statically linked. The problem with this is that many Linux distributions do not compile the boost static libs with {{-fPIC}}, so you get linker errors (see https://travis-ci.org/apache/arrow/jobs/139374716#L1430).
> In our CI builds, it would be best to avoid building boost from source each time, so I switched things to depend on boost shared libraries at runtime, but it would be nice to have the option to statically link assuming an appropriately-compiled boost. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)