It is unlikely that the compiling/linking is taking a lot of time.  .wixlibs 
may help some but if the majority of your time is spent moving files around you 
won't see a big win there.  It is easy to use .wixlibs, just use "lit.exe" on a 
bunch of .wixobjs then add the .wixlib on the command-line to "light.exe" 
instead of all the .wixobjs.

Merge Modules will only make the file processing slower because files are 
compressed into the Merge Module during Merge Module creation.  Then when used 
in an MSI the files are extracted from the Merge Module and laid out (often 
compressed) into the MSI image.

I think the feature you really are looking for is the "cabinet cache", assuming 
your files are compressed.  The cabinet cache works by creating the cabinet 
once then re-using the cabinet in multiple MSIs.  It's kinda' like incremental 
linking.

Check out the switches on light.exe for how to define where the cabinet cache 
should be.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy
Sent: Friday, May 09, 2008 12:03
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Using wixlibs or msm's to speed build process?


We have some installers that take a while to build, and we're currently doing a 
lot of releases that don't change a large portion of the files in the installer 
(much of the installer is 'content' rather than 'system' files).

Can anybody point me at a reference for how to use wixlibs or msm's to 
incrementally build our installer (i.e. build a wixlib or a msm for the content 
that just gets merged (hopefully quickly) into the output msi)?

Is this likely to improve things, or is it more likely that this will take just 
as long to build as the other process?

Thanks,
Kelly Leahy

**************************************************************************************
This communication is intended solely for the addressee and is
confidential. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful. Unless indicated
to the contrary: it does not constitute professional advice or opinions
upon which reliance may be made by the addressee or any other party,
and it should be considered to be a work in progress. Unless otherwise
noted in this email or its attachments, this communication does not form
a Statement of Actuarial Opinion under American Academy of Actuaries guidelines.
**************************************************************************************
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to