Hi Andrew, > I noticed that a few weeks ago you created a new directory in > the install hierarchy bin/boost to which the boost dlls get > copied. Is there a strong need for this separate directory?
Yes, I believe so. > I'm guessing that doing this makes it easier to create a > separate WiX component. It's used for a WiX component group, yes. I don't want to have to know the boost file names, which change based on the Boost version; but I do know the Qpid binaries' names specifically. The WiX harvesting tool doesn't have an option to filter, or I could just generate a group with *boost_*. The best I could come up with at the time, given the tools, was to put the Boost DLLs in their own directory. At install time they end up in 'bin' along with the other Qpid DLLs/exe. > It makes the simple zip package I'm trying to create harder. > Essentially this simple package is created by zipping up the > install hierarchy. As the boost DLLs need to be in the same > directory as the exes and dlls that use them when actually > deployed in my packaging they are all in the same bin directory. Can you move the boost directory content up a level before you zip it? Or use a command line switch to grab the content out of boost while zipping? Or, if you're open to building an installer, reuse the stuff in qpid/packaging/windows and package a subset of what's being done? -Steve --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
