On Fri, 2009-10-30 at 13:54 -0400, Steve Huston wrote: > ... > BTW, the plan of record (at least last I knew) was to migrate > everything to CMake and drop autoconf. I've noticed that many changes > made to Makefile.am don't necessarily make it over to CMakeLists.txt > and am wondering where the commitment level is for CMake transition > (in general with the primarily Linux folks, not Alan in particular).
As far as I'm aware the commitment level is as before. The issue is more that people forget or don't have enough experience with cmake to make the requisite changes. Once cmake is complete for linux targets (tests and install still need quite a bit of work) we can relegate autoconf to legacy only and then remove it (but that's a way in the future still I think). The simplest mistake is to add a new file and forget to put it in both build systems. It would be good to have a single file list that somehow fed both autoconf and cmake which would render that mistake impossible. Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
