Hi, I'm working on the Windows installer for Qpid 0.6. During the 0.5 -> 0.6 development cycle the build system changed to cmake-generated projects and along with that I put the additions in place to generate the Windows installer via Cpack which has built-in support for NSIS-based installers. The end result was that the 0.5 installer was done with WiX and the 0.6 installer (up til now) was based on NSIS.
The Cmake/Cpack changes also put the structure in place to generate other types of kits such as RPMs. I haven't tried to generate an RPM with it. I've been disappointed with the Cpack/NSIS experience and the resulting installer and would like to go back to WiX for the Windows installer. I would like to better integrate the WiX mechanisms into the cmake scheme as part of this. I would also like to remove the NSIS-specific parts of the Cpack stuff, leaving what's needed for RPMs, etc. in place. Does anyone have an issue with my removing the NSIS-specific parts of the cmake builds, and replacing that with WiX? This has no affect on plain, every-day development - it would only affect people who are building binary installer kits. I believe I'll be able to mostly automate the WiX process, but it's possible there will be some manual items needed, which I'll document as they come up. I'm happy to bid NSIS good-bye, but if anyone out there has noticed NSIS support in the development process and become attached to it, please yell. Quickly. Thanks, -Steve -- Steve Huston, Riverace Corporation Total Lifecycle Support for Your Networked Applications http://www.riverace.com --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
