You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Till Toenshoff (JIRA)" <ji...@apache.org> on 2018/11/25 16:24:00 UTC

[jira] [Commented] (MESOS-9406) Allow for optionally unbundled leveldb from CMake builds.

    [ https://issues.apache.org/jira/browse/MESOS-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698217#comment-16698217 ] 

Till Toenshoff commented on MESOS-9406:
---------------------------------------

Just noticed that our autotools based unbundling of leveldb also resorts into linking it dynamically - doing the same for CMake should be fine then.

> Allow for optionally unbundled leveldb from CMake builds.
> ---------------------------------------------------------
>
>                 Key: MESOS-9406
>                 URL: https://issues.apache.org/jira/browse/MESOS-9406
>             Project: Mesos
>          Issue Type: Improvement
>          Components: build, cmake
>    Affects Versions: 1.8.0
>            Reporter: Till Toenshoff
>            Assignee: Till Toenshoff
>            Priority: Minor
>              Labels: cmake, unbundled-dependencies
>
> Following the example of unbundled libevent and libarchive, we should allow for unbundled leveldb if the user wishes so.
> For leveldb, this task is not as trivial as one would hope due to the fact that we link leveldb statically. This forces us to satisfy leveldb's strong dependencies against gpertools (tcmalloc) as well as snappy.
> Alternatively, we would resort into linking leveldb dynamically, solving these issues.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)