[WiX-users] Building a multi-language msi....

[Tony]

I think we are doing this right, but I want to be sure as it seems
painfully tedious.

Here is a high-level sequence of what we are currently doing to build
a single msi that supports 8 languages (en-us, 4 euro, Japanese and 2
Chinese scripts)...

1. Compile all component binaries.
2. Build a few wixlibs that contain those components.
3. Build en-us version of msi (including our custom action dll)
4. Copy en-us version of the msi so that it becomes our "base" msi
5. Build a localized version of the msi (built using the existing
en-us version our custom action dll)
6. Create transform file using msitran.exe
7. Merge that transform file into our base msi using wisubstg.vbs
8. Repeat steps 5-7 for remaining 6 languages
9. Specify supported languages in the merged msi using wilangid.vbs

The entire process is repeated to generate a x64 version of the msi.

Does this seem correct?

[Rob Mensching]

Fundamentally, yes.

You can optimize a bit by building a .wixout at step 3 then running light
with a different .wxl to generate each MSI from the .wixout. That'll save
some linking time.

Post by Tony
I think we are doing this right, but I want to be sure as it seems
painfully tedious.
Here is a high-level sequence of what we are currently doing to build
a single msi that supports 8 languages (en-us, 4 euro, Japanese and 2
Chinese scripts)...
1. Compile all component binaries.
2. Build a few wixlibs that contain those components.
3. Build en-us version of msi (including our custom action dll)
4. Copy en-us version of the msi so that it becomes our "base" msi
5. Build a localized version of the msi (built using the existing
en-us version our custom action dll)
6. Create transform file using msitran.exe
7. Merge that transform file into our base msi using wisubstg.vbs
8. Repeat steps 5-7 for remaining 6 languages
9. Specify supported languages in the merged msi using wilangid.vbs
The entire process is repeated to generate a x64 version of the msi.
Does this seem correct?
--
Tony
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and
easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users

[Tony]

Thanks.

Post by Rob Mensching
Fundamentally, yes.
You can optimize a bit by building a .wixout at step 3 then running light
with a different .wxl to generate each MSI from the .wixout. That'll save
some linking time.

Post by Tony
I think we are doing this right, but I want to be sure as it seems
painfully tedious.
Here is a high-level sequence of what we are currently doing to build
a single msi that supports 8 languages  (en-us, 4 euro, Japanese and 2
Chinese scripts)...
1. Compile all component binaries.
2. Build a few wixlibs that contain those components.
3. Build en-us version of msi (including our custom action dll)
4. Copy en-us version of the msi so that it becomes our "base" msi
5. Build a localized version of the msi (built using the existing
en-us version our custom action dll)
6. Create transform file using msitran.exe
7. Merge that transform file into our base msi using wisubstg.vbs
8. Repeat steps 5-7 for remaining 6 languages
9. Specify supported languages in the merged msi using wilangid.vbs
The entire process is repeated to generate a x64 version of the msi.
Does this seem correct?
--
Tony
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and
easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users

--
virtually, Rob Mensching - http://RobMensching.com LLC
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users