sapling/contrib/wix
2017-07-21 11:26:51 -05:00
..
contrib.wxs wix: contrib/sample.hgrc is no more 2014-09-15 09:36:12 -05:00
COPYING.rtf copyright: update to 2016 2016-01-21 21:15:52 +00:00
defines.wxi wix: add support for x64 native MSI packages 2010-11-26 17:40:13 -06:00
dist.wxs wix: update list of necessary pyd files 2017-07-21 11:26:51 -05:00
doc.wxs wix: add support for x64 native MSI packages 2010-11-26 17:40:13 -06:00
guids.wxi wix: update list of necessary pyd files 2017-07-21 11:26:51 -05:00
help.wxs wix: only one KeyPath is allowed per Component 2017-05-06 10:18:34 -05:00
hg.cmd wix: switch Mercurial Windows installer to use py2exe --bundle 3 2010-11-26 16:18:19 -06:00
i18n.wxs codingstyle: remove trailing spaces in various text files 2013-04-17 03:40:18 +02:00
locale.wxs wix: add 'ro' and 'ru' locales 2017-05-25 23:42:37 -04:00
mercurial.wxs misc: replace domain of mercurial ML address by mercurial-scm.org 2017-02-11 00:23:53 +09:00
README.txt help: fix some instances of 'the the' 2012-07-26 02:54:13 +02:00
templates.wxs hgweb: rename linerangelog.js as followlines.js 2017-04-03 10:02:55 +02:00

WiX installer source files
==========================

The files in this folder are used by the thg-winbuild [1] package
building architecture to create a Mercurial MSI installer.   These files
are versioned within the Mercurial source tree because the WXS files
must kept up to date with distribution changes within their branch.  In
other words, the default branch WXS files are expected to diverge from
the stable branch WXS files.  Storing them within the same repository is
the only sane way to keep the source tree and the installer in sync.

The MSI installer builder uses only the mercurial.ini file from the
contrib/win32 folder, the contents of which have been historically used
to create an InnoSetup based installer.  The rest of the files there are
ignored.

The MSI packages built by thg-winbuild require elevated (admin)
privileges to be installed due to the installation of MSVC CRT libraries
under the C:\WINDOWS\WinSxS folder.  Thus the InnoSetup installers may
still be useful to some users.

To build your own MSI packages, clone the thg-winbuild [1] repository
and follow the README.txt [2] instructions closely.  There are fewer
prerequisites for a WiX [3] installer than an InnoSetup installer, but
they are more specific.

Direct questions or comments to Steve Borho <steve@borho.org>

[1] http://bitbucket.org/tortoisehg/thg-winbuild
[2] http://bitbucket.org/tortoisehg/thg-winbuild/src/tip/README.txt
[3] http://wix.sourceforge.net/