Castro, Edwin G. (Hillsboro <Edwin.Castro <at> Fiserv.com> writes: > > This much less a WiX issue and more of a MSBuild issue as that's what is used to perform a build in Visual Studio 2010. > > MSBuild has the concept of Target Inputs and Outputs which it uses to determine whether a target need to be > executed in incremental build scenarios. > > The wix2010.targets file imported by your .wixproj project will need to be customized to make this work as > you expect. The changes will likely need to completely replace some of the targets defined in > wix2010.targets with versions that make use of Target Inputs and Outputs in a fashion that is consistent > with your expectations. > > > -----Original Message----- > > From: Sean Leonard [mailto:lists+sourceforge <at> seantek.com] > > > > Anyway, the specific question (so that this is not just a naked job > > post) is: how can the WiX files be setup so that they have proper incremental > > build support in Visual Studio 2010 with multiple language source files? The > > process is: > > > > Take 3 input files (DLLs, EXEs) -> > > Take 10 localizations (en-us, ja-jp, fr-fr, etc.) -> Create master msi Create 10 > > transforms stash the transforms somewhere Use EmbedTransform to create > > one final msi file with the 10 transforms, so the software can ship as one MSI > > > > When an incremental build happens: > > * If zero input files have changed and the final msi has not changed, NO build > > should occur. We're done. > > * If one of the 3 input files have changed, create the initial msi, and use > > embedtransform to create one file msi from the stashed transforms. > > (This sounds implausible, but, I have looked at the transforms and they are > > for all intents and purposes the same. There seems to be no reason to > > constantly rebuild the transforms.) > > * Only if one of the localizations has changed, for example, one of the strings > > has changed, then the 10 transforms should be regenerated. > > >
Message me at egcastr at gmail (that's not a spelling error, there is no o at the end) and I'll take a look at this more carefully. I need to do a little spelunking in the wix2010.targets file before I'm comfortable providing a workaround. -- Edwin G. Castro ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
