The WiX toolset works somewhat like a C++ toolset. Candle is a 'compiler'
which parses your source code and turns it into 'object code' - in this
case, effectively writing the rows that will be written to the MSI, with
placeholders where necessary if a reference is not resolved within this
fragment.
Light, the linker, takes multiple 'object files', including libraries of
object files (.wixlib files) and libraries embedded in extension DLLs, and
combines them into an MSI, MSM, or other appropriate output.
You wouldn't pass a .wxs file to light - it doesn't understand it. You have
to first compile it with candle.
In this particular case, module.wxs isn't actually needed as product.wxs is
self-contained. Its presence on the candle command line is misleading. In
the version of the tutorial I'm looking at, it's not referenced. If it were
needed then you would put the output from candle, module.wixobj, on the
command line.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Siegfried
Heintze (Aditi)
Sent: 28 March 2008 23:16
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] How to compile and link project example?
In the v3 chm file tutorial, they give you this instructions:
candle "module.wxs" "product.wxs"
light product.wixobj
msiexec /i product.msi /l*v product.log
What is the reason that the light command line does not include module.wxs?
Thanks,
Siegfried
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
