Okay, there is clearly something fundamentally busted. Can you open a bug with
as much information as possible? There is a way through this process (I know
plenty of people are successfully using it) but you have obviously found a case
that doesn't work.
From: Fairweather, James [mailto:[EMAI
OK, that's good to know about what the various tools are designed to output.
Unfortunately in this case calling torch on the wixmst file returns an error
similar to the one light gave me:
Ø Torch.exe en-us.wixmst -out en-us.mst
C:\Documents and Settings\jamesf\Local Settings\Temp\nkwvms
Yeah, this is easy but the error message didn't help you (I've given it to
Peter and he'll try to fix it tonight). "light" is for creating "MSI/MSM"
files. "torch" is for creating "MST" files. "pyro" is for creating "MSP"
files. Armed with that knowledge, hopefully it is clear that your fina
Thank-you , Rob and Josh. That looks like it should work, but it fails with a
not-very-helpful error message:
I have produced a ".wixmst" file from torch like so:
Ø torch.exe -t language -v -p -xi -xo C:\eao neutral.wixout en-us.wixout -out
en-us.wixmst
Now call light on the wixmst fil
You're right on track. Last step is to take the .wixout (should have been
named ".wixmsi" to match the other things but .wixout came first) and feed it
back into light.exe. Light will finish processing the .wixout into MSI. Is
that detailed enough or am I missing a step?
From: [EMAIL PROTECT
5 matches
Mail list logo