We're trying to make it faster. We're currently using a wixout file to get us halfway through the process. Yet, it still takes a while since we are localizing for eight languages. Our latest idea is to stop reusing the wixout in such a synchronous way. By that I mean that we use a batch file that calls each language one after the other. So, we always have to wait for the current language to finish before moving on. We plan to use the wixout in several threads at the same time by using a "start" command in our batch script.
The main problem is the CAB file. We're using -reusecab and -cc, but it didn't like us accessing the same CAB file more than once at the same time. So, we plan to make several copies of it, one for each language. That way, each language has its own copy, it's own cabinet cache directory. Earlier, I'd thought that using the -bf switch would help with the speed. It probably did, but it came with its own problem. Using it caused any custom bitmaps we had to not work. It was weird. We were using WixVariables and the variables didn't seem to be expanded in the .wixout. Yet, when we built the MSI, our bitmaps were never there. It was always the defaults from the WiX source. My only guess is that -bf bound the bitmaps into the .wixout using the default paths, even though the variables in the XML hadn't indicated that. Just a guess though. We dropped -bf and that probably hurt our speed. I've looked through the source code for Light and I think I've generally got a good idea about the order of things. I'm just not sure we've found all the ways to optimize. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/What-does-Light-do-tp4946163p4963003.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
