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) If you want to have a look, here are a few notes (I'll expand on this and fix the README before things are done): - The main description of the build/configure is in cpp/CMakeLists.txt. There's also a CMakeLists.txt in qpid/cpp/src, and that's where most of the real content is at this point. - The recommended way to try a build is to create a subdir under qpid/cpp for your build, then configure and build in the subdir. For example: cd qpid/cpp mkdir mybuild cd mybuild ccmake .. On Windows, the last step is CMakeSetup (there's probably a shortcut on the desktop from the cmake install) That will display a screen for you to select configure options, type of build, etc. then generate the desired makefiles. After generating the makefiles, build as usual. Don't worry... For scripted or expert builds, there's a command-line shortcut to the ccmake/CMakeSetup but to get used to it the above is a good start. Please let me know if you run into problems, questions, etc. Thanks, -Steve --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
