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

Frank Scholten commented on MESOS-3139:
---------------------------------------

Trying to post a review but it fails

{code}
frank@franktop:~/src/mesos$ ./support/post-reviews.py 
--server=https://reviews.apache.org --tracking-branch=origin/master 
--target-groups=mesos --open
Running 'rbt post' across all of ...
0949e6be6a4260933172ea93acc4bc0592c1e2f1 - (HEAD -> MESOS-3139) Added first 
draft CMake build docs. (4 minutes ago)

Creating diff of:
0949e6be6a4260933172ea93acc4bc0592c1e2f1 - (HEAD -> MESOS-3139) Added first 
draft CMake build docs.

Press enter to continue or 'Ctrl-C' to skip.

Review request #47723 posted.

https://reviews.apache.org/r/47723/
https://reviews.apache.org/r/47723/diff/
[10746:10777:0523/133438:ERROR:nss_util.cc(839)] After loading Root Certs, 
loaded==false: NSS error code: -8018
Created new window in existing browser session.
Failed to execute: 'git commit --amend -m Added first draft CMake build docs.


Review: [10746:10777:0523/133438:ERROR:nss_util.cc(839)] After loading Root 
Certs, loaded==false: NSS error code: -8018
':
Usage: ./mesos-split.py <filename>...
Error: No line in the commit message summary may exceed 72 characters.
{code}

> 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: 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)

Reply via email to