On Tue, 2009-04-21 at 15:01 -0400, Steve Huston wrote: > Hi Qpideers, > > A while back I mentioned that Microsoft funded efforts to improve the > qpid C++ build process, align the Linux/UNIX and Windows build > processes and end the problem where the Windows builds are a step > behind the Linux builds when files change. > > As mentioned here previously, the initial approach to this is to try > Cmake (www.cmake.org) and that has been going along well. The basic > libraries (common, client, broker, cluster, ssl) and broker build are > integrated. It's not yet ready for prime time, as the test build and > execution isn't yet integrated. That'll probably be ready for general > evaluation within a couple of weeks, but for the adventurous among us > who want an early look, the work is happening on the subversion cmake > branch (https://svn.apache.org/repos/asf/qpid/branches/cmake)
Can this work sit alongside the existing build systems? If so I don't think there's any reason not to do this work on the trunk. It would certainly be an easier transition if the cmake infrastructure doesn't happen at a stroke, dismantling the existing build system, but overlapping if possible for a short while (say a week or two). It this isn't possible now (say due to some necessary changes in the source) then is it possible with a restricted amount of work to the existing build systems to make it so? Thanks for this work - I'll be very glad to get shot of libtool - the small amount of kde compiling I've done makes me like the cmake approach. Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
