You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alex Clemmer (JIRA)" <ji...@apache.org> on 2016/12/05 04:18:58 UTC

[jira] [Updated] (MESOS-3106) Extend CMake build system to support building against third-party libraries from either the system or the local Mesos rebundling

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

Alex Clemmer updated MESOS-3106:
--------------------------------
    Labels: cmake mesosphere microsoft windows-mvp  (was: build cmake)

> Extend CMake build system to support building against third-party libraries from either the system or the local Mesos rebundling
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-3106
>                 URL: https://issues.apache.org/jira/browse/MESOS-3106
>             Project: Mesos
>          Issue Type: Task
>          Components: cmake
>            Reporter: Alex Clemmer
>            Assignee: Alex Clemmer
>              Labels: cmake, mesosphere, microsoft, windows-mvp
>
> Currently Mesos has third-party dependencies of two types: (1) those that are expected to be on the system (such as APR, libsvn, _etc_.), and (2) those that have been historically bundled as tarballs inside the Mesos repository, and are not expected to be on the system when Mesos is installed (these are located in the `3rdparty/` directory, and includes things like boost and glog).
> For type (2), the MVP of the CMake-based build system will always pull down a fresh tarball from an external source, instead of using the bundled tarballs in the `3rdparty/` folder.
> However, many CI systems do not have Internet access, so in the long term, we need to provide many options for getting these dependencies.



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