[mailto:bev...@mesosphere.com]
Sent: Monday, August 28, 2017 2:41 AM
To: dev@mesos.apache.org
Subject: Re: CMake build refactoring
Hi Andrew,
thanks for working on this, it looks very nice.
Is there a policy on how to handle changes to the build system before the
official deprecation of autotools
Hi Andrew,
thanks for working on this, it looks very nice.
Is there a policy on how to handle changes to the build system before the
official deprecation of autotools? I.e., should should reviewers require
that new features are added only to autoconf, only to CMake, or to both?
Thanks,
Benno
Hi Zhitao,
1) I talked with Joe and confirmed that we're targeting 1.5 for this
chain.
2) For Mesos modules, the included example modules are built, but I
don't have an external example. I think the easiest approach to doing so
is to include Mesos as a submodule and then
Hi Andrew,
Thank you for the great work. Really looking forward to see a more
structured dependency graph.
A couple of questions:
1) is there a target version of this work? Will the chain land on 1.5?
2) For people who maintains Mesos modules, is there a example build of how
people can arrange
+1
On Fri, Aug 25, 2017 at 12:08 PM, wrote:
> I have the Java libraries building now on both Linux and Windows (though
> the initial setup on Windows is a bit annoying to get all the tools in the
> right place, I'd like to follow up this chain with a `docs/cmake.md`
I have the Java libraries building now on both Linux and Windows (though
the initial setup on Windows is a bit annoying to get all the tools in
the right place, I'd like to follow up this chain with a `docs/cmake.md`
with all the odd little bits of information).
I also enabled the ZooKeeper
This is great to hear. Thanks for your perseverance on making this happen
Andy!
Btw, do we build Java and Python libraries too now?
Once we land the CMake changes, lets make sure to update
`support/docker-build.sh` to make sure it is continuously being tested on
our CI.
On Fri, Aug 25, 2017 at