Arnette, Bill wrote: > So how do you replace a merge module with a wixlib. A merge module has > a cab with the files to be installed in it. AFAIK, a wixlib has no way > transporting the files to be installed to the final MSI. So it seems to > me that to use a wixlib, you need the wixlib and the binaries to be > installed by the wixlib. Correct? >
That's true in WiX v2. In WiX v3, Derek got rid of that limitation to put the last stake in merge modules; .wixlibs in v3 can hold their files. > The problem we have is that we are trying to include some components > from an older product with a newer product. The older product > references the binaries to be installed with a compiler variable set to > "..\stage\product\bin" while the new product references them with > "stage\product\bin". The newer product is the staging convention going > forward. So it seems we will have to revamp the older product's build > to stage everything like the new product. Correct? > You can pass multiple -b switches to light to bind different directories, as long as there are no duplicate files that would end up picking up the wrong files. -- sig://boB http://bobs.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
