[
https://issues.apache.org/jira/browse/MESOS-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Clemmer updated MESOS-3380:
--------------------------------
Description:
libev does not have a standalone Windows build, which means that using it to
support Mesos on Windows would require direct integration into our build system
and, perhaps, our code path.
For this reason, we need to use libevent, but this is also a big decision, as
the libevent support is still provisional. So, a good solution will involve:
* Failing Windows builds if they don't pass in `-DENABLE_LIBEVENT` to opt in to
libevent
* During build failure, informing them that libevent is a much less-exercised
code path
* Writing logic to configure/build/install libevent locally
was:Windows will probably require libevent to work. This means we need to
insert the code to retrieve, build, and link against it for the Windows path,
since it isn't rebundled and distributed as part of Mesos.
> Include libevent in Windows CMake build
> ---------------------------------------
>
> Key: MESOS-3380
> URL: https://issues.apache.org/jira/browse/MESOS-3380
> Project: Mesos
> Issue Type: Task
> Components: build
> Reporter: Alex Clemmer
> Assignee: Alex Clemmer
> Labels: build, cmake, mesosphere
>
> libev does not have a standalone Windows build, which means that using it to
> support Mesos on Windows would require direct integration into our build
> system and, perhaps, our code path.
> For this reason, we need to use libevent, but this is also a big decision, as
> the libevent support is still provisional. So, a good solution will involve:
> * Failing Windows builds if they don't pass in `-DENABLE_LIBEVENT` to opt in
> to libevent
> * During build failure, informing them that libevent is a much less-exercised
> code path
> * Writing logic to configure/build/install libevent locally
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
