[
https://issues.apache.org/jira/browse/MESOS-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15843776#comment-15843776
]
Joseph Wu commented on MESOS-3542:
----------------------------------
{code}
commit 8bbfa5108ba4e5d2fe1b584bd8103274bc6631fc
Author: Alex Clemmer <clemmer.alexan...@gmail.com>
Date: Fri Jan 27 12:21:33 2017 -0800
CMake: Added source groups for libprocess.
This uses the recently-introduced CMake function, `GROUP_SOURCE`, to
automatically group libprocess sources. This makes sources appear
in a sensible directory structure in certain supported IDE's.
Review: https://reviews.apache.org/r/55604/
commit 7cd8c6a8589d1dab31752f178b625ccec311a436
Author: Alex Clemmer <clemmer.alexan...@gmail.com>
Date: Thu Jan 26 14:12:16 2017 -0800
CMake: Transitioned Stout to automatic source grouping.
Stout currently manually groups its source code by folder in order to
present the source nicely in IDEs like XCode and Visual Studio.
With the recently-introduced CMake function, `GROUP_SOURCE`, this
process is automated away. This commit will remove these manual groups
and replace it with a call to this function.
Review: https://reviews.apache.org/r/55600/
commit 8b31bd2b075dce94a10f6067f517fcbcb88a40ea
Author: Alex Clemmer <clemmer.alexan...@gmail.com>
Date: Thu Jan 26 14:05:53 2017 -0800
CMake: Added `GroupSource` function to automate IDE source grouping.
CMake allows users to declare groups of source files, which it uses to
(among other things) present source in a directory-like tree of files in
IDEs like XCode and Visual Studio.
Currently this is a manual process: we group the source in each folder
manually and declare it as a source group to CMake.
This commit will introduce a CMake macro that automates this process
away, providing control over many aspects, such as where the group tree
should be rooted, what the root should be named, and so on.
This macro indirectly partially addresses MESOS-3542, which will help us
to separate out Mesos builds into many libraries, rather than one
single, monolithic libmesos.
Review: https://reviews.apache.org/r/55599/
{code}
> Separate libmesos into compiling from many binaries.
> ----------------------------------------------------
>
> Key: MESOS-3542
> URL: https://issues.apache.org/jira/browse/MESOS-3542
> Project: Mesos
> Issue Type: Epic
> Components: cmake
> Reporter: Alex Clemmer
> Assignee: Alex Clemmer
> Labels: cmake, mesosphere, microsoft, windows-mvp
>
> Historically libmesos is built as a huge monolithic binary. Another idea
> would be to build it from a bunch of smaller libraries (_e.g._, libagent,
> _etc_.).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
