Hi Andrew, > 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.
Doesn't that belie a fairly low commitment? It's been in place a while now. People can ask when it's unclear. Or just give it a try - it's pretty easy to figure out how to add a file to a list. > 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). Is someone going to help out? I've been adding the install stuff for both Windows and Linux; the test stuff is more dependent on the python changes going over to cmake (https://issues.apache.org/jira/browse/QPID-2127) - the location of qpid-python-test being different from where it is in the source tree is what's primarily holding that up at this point. > 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. If it were an easy task to build such a list mechanism, doing so would just delay the cmake move. -Steve --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
