##// END OF EJS Templates
contrib: migrate off of a couple of bitbucket URLs...
Matt Harbison -
r50068:90f7d827 default
parent child Browse files
Show More
@@ -1,57 +1,57 b''
1 1 WiX Installer
2 2 =============
3 3
4 4 The files in this directory are used to produce an MSI installer using
5 5 the WiX Toolset (http://wixtoolset.org/).
6 6
7 7 The MSI installers require elevated (admin) privileges due to the
8 8 installation of MSVC CRT libraries into the Windows system store. See
9 9 the Inno Setup installers in the ``inno`` sibling directory for installers
10 10 that do not have this requirement.
11 11
12 12 Requirements
13 13 ============
14 14
15 15 Building the WiX installer requires a Windows machine.
16 16
17 17 The following system dependencies must be installed:
18 18
19 19 * Python 3.6+ (to run the ``packaging.py`` script)
20 20
21 21 Building
22 22 ========
23 23
24 24 The ``packaging.py`` script automates the process of producing an MSI
25 25 installer. It manages fetching and configuring non-system dependencies
26 26 (such as gettext, and various Python packages). It can be run from a
27 27 basic cmd.exe Window (i.e. activating the MSBuildTools environment is
28 28 not required).
29 29
30 30 From the prompt, change to the Mercurial source directory. e.g.
31 31 ``cd c:\src\hg``.
32 32
33 33 Next, invoke ``packaging.py`` to produce an MSI installer.::
34 34
35 35 $ py -3 contrib\packaging\packaging.py \
36 36 wix --pyoxidizer-target x86_64-pc-windows-msvc
37 37
38 38 If everything runs as intended, dependencies will be fetched and
39 39 configured into the ``build`` sub-directory, Mercurial will be built,
40 40 and an installer placed in the ``dist`` sub-directory. The final line
41 41 of output should print the name of the generated installer.
42 42
43 43 Additional options may be configured. Run ``packaging.py wix --help``
44 44 to see a list of program flags.
45 45
46 46 Relationship to TortoiseHG
47 47 ==========================
48 48
49 49 TortoiseHG uses the WiX files in this directory.
50 50
51 51 The code for building TortoiseHG installers lives at
52 https://bitbucket.org/tortoisehg/thg-winbuild and is maintained by
52 https://foss.heptapod.net/mercurial/tortoisehg/thg-winbuild and is maintained by
53 53 Steve Borho (steve@borho.org).
54 54
55 55 When changing behavior of the WiX installer, be sure to notify
56 56 the TortoiseHG Project of the changes so they have ample time
57 57 provide feedback and react to those changes.
@@ -1,97 +1,97 b''
1 1 ; System-wide Mercurial config file.
2 2 ;
3 3 ; !!! Do Not Edit This File !!!
4 4 ;
5 5 ; This file will be replaced by the installer on every upgrade.
6 6 ; Editing this file can cause strange side effects on Vista.
7 7 ;
8 ; http://bitbucket.org/tortoisehg/stable/issue/135
8 ; https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/135
9 9 ;
10 10 ; To change settings you see in this file, override (or enable) them in
11 11 ; your user Mercurial.ini file, where USERNAME is your Windows user name:
12 12 ;
13 13 ; XP or older - C:\Documents and Settings\USERNAME\Mercurial.ini
14 14 ; Vista or later - C:\Users\USERNAME\Mercurial.ini
15 15
16 16
17 17 [ui]
18 18 ; editor used to enter commit logs, etc. Most text editors will work.
19 19 ; editor = notepad
20 20 ; show changed files and be a bit more verbose if True
21 21 ; verbose = True
22 22 ; colorize commands output
23 23 ; color = auto
24 24
25 25 ; username data to appear in commits
26 26 ; it usually takes the form: Joe User <joe.user@host.com>
27 27 ; username = Joe User <j.user@example.com>
28 28
29 29 ; In order to push/pull over ssh you must specify an ssh tool
30 30 ;ssh = "C:\Progra~1\TortoiseSVN\bin\TortoisePlink.exe" -ssh -2
31 31 ;ssh = C:\cygwin\bin\ssh
32 32
33 33 ;
34 34 ; For more information about mercurial extensions, start here
35 35 ; https://www.mercurial-scm.org/wiki/UsingExtensions
36 36 ;
37 37 ; Extensions shipped with Mercurial
38 38 ;
39 39 [extensions]
40 40 ;acl =
41 41 ;blackbox =
42 42 ;bugzilla =
43 43 ;children =
44 44 ;churn =
45 45 ;convert =
46 46 ;eol =
47 47 ;extdiff =
48 48 ;fetch =
49 49 ;gpg =
50 50 ;hgk =
51 51 ;highlight =
52 52 ;histedit =
53 53 ;interhg =
54 54 ;largefiles =
55 55 ;keyword =
56 56 ;mq =
57 57 ;notify =
58 58 ;pager =
59 59 ;patchbomb =
60 60 ;progress =
61 61 ;purge =
62 62 ;rebase =
63 63 ;record =
64 64 ;relink =
65 65 ;schemes =
66 66 ;share =
67 67 ;transplant =
68 68 ;win32mbcs =
69 69 ;zeroconf =
70 70
71 71 ;
72 72 ; Define external diff commands
73 73 ;
74 74 [extdiff]
75 75 ;cmd.bc3diff = C:\Program Files\Beyond Compare 3\BCompare.exe
76 76 ;cmd.vdiff = C:\Progra~1\TortoiseSVN\bin\TortoiseMerge.exe
77 77 ;cmd.vimdiff = gvim.exe
78 78 ;opts.vimdiff = -f "+next" "+execute 'DirDiff' fnameescape(argv(0)) fnameescape(argv(1))"
79 79
80 80
81 81 [hgk]
82 82 ; Replace the following with your path to hgk, uncomment it and
83 83 ; install ActiveTcl (or another win32 port like tclkit)
84 84 ; path="C:\Program Files\Mercurial\Contrib\hgk.tcl"
85 85 ; vdiff=vdiff
86 86
87 87
88 88 ;
89 89 ; The git extended diff format can represent binary files, file
90 90 ; permission changes, and rename information that the normal patch format
91 91 ; cannot describe. However it is also not compatible with tools which
92 92 ; expect normal patches. so enable git patches at your own risk.
93 93 ;
94 94 [diff]
95 95 ;git = false
96 96 ;nodates = false
97 97
General Comments 0
You need to be logged in to leave comments. Login now