I think I read something about cross compiling now that I think about it, I don't think maintaining two build systems is of any interest but I was just curious. I don't have any major problem with autoconf/automake as long as I have nothing more to do with it than "./configure" ;) The only time I actually tried to use it for a personal project was marked with a black stone and I will certainly won't do it again ^^ there is also the out of tree compilation which is really nice. On 29 August 2013 16:25, Bruce Mitchener <bruce.mitchener@xxxxxxxxx> wrote: > On Thu, Aug 29, 2013 at 9:18 PM, Martin Sustrik <sustrik@xxxxxxxxxx>wrote: > >> Hi Bruce, Julien, >> >> The main reason is to ease the maintenance burden and QA. It's really >> hard to keep single build system working, let alone two. >> >> That being said, if there are volunteers to keep CMake build system >> synchronised with autotools build system, I'll be happy to hand over the >> responsibility :) >> >> If so, I would start with adjusting our CI cluster ( >> http://build.nanomsg.org/**waterfall <http://build.nanomsg.org/waterfall>) >> to test CMake builds in addition to autotools builds. Adding some Windows >> boxes to the cluster would help as well (CMake differs from autotools by >> its ability to produce MSVC projects). > > > There was a single working build system that worked on all platforms > before. I think the question is why this actually needed to change (outside > of ideological reasons). > > - Bruce > >