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-3139) Incorporate CMake into standard documentation

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

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

> Incorporate CMake into standard documentation
> ---------------------------------------------
>
>                 Key: MESOS-3139
>                 URL: https://issues.apache.org/jira/browse/MESOS-3139
>             Project: Mesos
>          Issue Type: Task
>          Components: cmake
>            Reporter: Alex Clemmer
>            Assignee: Alex Clemmer
>              Labels: cmake, mesosphere, microsoft, windows-mvp
>
> Right now it's anyone's guess how to build with CMake. If we want people to use it, we should put up documentation. The central challenge is that the CMake instructions will be slightly different for different platforms.
> For example, on Linux, the gist of the build is basically the same as autotools; you pull down the system dependencies (like APR, _etc_.), and then:
> ```
> ./bootstrap
> mkdir build-cmake && cd build-cmake
> cmake ..
> make
> ```
> But, on Windows, it will be somewhat more complicated. There is no bootstrap step, for example, because Windows doesn't have bash natively. And even when we put that in, you'll still have to build the glog stuff out-of-band because CMake has no way of booting up Visual Studio and calling "build."
> So practically, we need to figure out:
> * What our build story is for different platforms
> * Write specific instructions for our "core" target platforms.



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