Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


That is a reason why I suggest to leave the user make its own choice
among the available dictionaries (only one, all, whatever he want).

Which is exactly what the user can do in a "custom" installation.

So I restate one of my questions : what is the tool used to code the
installer ?

A bunch of source data files in scp2 (used on all platforms), a pile of Perl run from 
solenv/bin/make_installer.pl, a number of template .idt files for Windows Installer, which are then 
mangled by the Perl code and produces stuff fed to Windows Installer tools like msidb,  ending up 
with a .msi file, one or several .cab files, and optionally a number of .mst files.

Then there is a setup.exe which is plain C++ code which is a small program that just runs msiexec 
on the .msi file, telling it which installer UI localisation to use.

And finally all this can optionally be wrapped by NSIS into a single executable file installer like 
the ones that we offer.

--tml



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.