[
https://issues.apache.org/jira/browse/MESOS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680543#comment-14680543
]
Alex Clemmer commented on MESOS-3139:
-------------------------------------
Thanks so much for the work [[email protected]]!
I've left comments in the reviews. For Ryan Dahl's http parser lib, don't worry
about it just yet -- I believe it's a headers-only file anyway. For libev, we
have ideas, but we're not yet to a point where we are prepared to give you an
answer about how we're going to handle it in the short term. So we'll just have
to regroup on that, sorry!
> Incorporate CMake into standard documentation
> ---------------------------------------------
>
> Key: MESOS-3139
> URL: https://issues.apache.org/jira/browse/MESOS-3139
> Project: Mesos
> Issue Type: Task
> Components: build
> Reporter: Alex Clemmer
> Assignee: Alex Clemmer
> Labels: build, cmake, mesosphere
>
> 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)
