forked from TortoiseGit/tortoisesvn
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathbuild.txt
174 lines (133 loc) · 7.04 KB
/
build.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
// To build this file, execute "nant APIDocs"
// After that, you can read the compiled version at doc\output\TortoiseSVNAPI.chm
/**
\page build Build instructions
\section Introduction Introduction
Compiling TortoiseSVN is not very difficult, but it requires several steps
to finish, at least when you do it the first time.
Unlike other big open source projects, once you have built all the libraries
TortoiseSVN depends on, you can use the familiar VisualStudio IDE to build
and debug the binaries. No need to run the build script for every little change.
So don't give up if you read through the next section you will find all the requirements.
You need to perform most steps only once.
\section Requirements Requirements
\subsection Requirements1 First, you need to install the compiler package.
-# You need VS2017 to allow building of the full TortoiseSVN package.
If you don't have Visual Studio yet, you can download and install
the community edition for free. Make sure to leave the checkbox for
"Microsoft Foundation library" checked in the first installer dialog.
If you want to build the msi make sure the "Tools for Redistributing
Applications" are installed.
\subsection Requirements2 Next you need to install some utilities/programs.
- Java runtime https://www.java.com
- Python 2.6(\b 1 \b 3) https://www.python.org/windows/
- libxml2 python bindings(\b 2) http://users.skynet.be/sbi/libxml-python/
- Perl http://strawberryperl.com/releases.html
or
https://www.activestate.com/Products/ActivePerl/
- WiX 3.10(\b 1) http://wixtoolset.org/
- NAnt 0.92(\b 1) http://nant.sourceforge.net
(\b 1) Add the paths of the binaries to the PATH environment variable. You may have to
logoff/logon to make the new environment variables take effect!
Also make sure to "unblock" the zip file before extracting when you install NAnt.
(\b 2) right-click on the installer file and "run as administrator" to install it.
(\b 3) use 32 bit installer (even on x64 OS)
\subsection Requirements3 Finally, you may need to install some fonts.
- Arabic(\b Optional) http://www7.bev.net/civic/icb/quran/Iqraa_ttf.zip
- Japanese(\b Optional) msgothic.ttc and msmincho.ttc should be available
if you activate support for international fonts in your OS.
- Chinese(\b Optional) simhei.ttf and simsun.httf should be available
if you activate support for international fonts in your OS.
\section Preparations Preparations
Now you're almost ready. Only a few more steps to do:
- create a new folder on your harddisk, e.g. SVN. Make sure you have at least
4 GB of free space left!!!
- Checkout the TortoiseSVN sources from the Subversion repository into
SVN\TortoiseSVN. Make sure the path does not have '[' or ']' chars in it!
- Make a copy of the file default.build.user.tmpl in the TortoiseSVN root folder and
rename that copy to default.build.user. Then adjust the paths as mentioned
in that file. You may leave it unchanged if you installed / copied everything
into the suggested default paths.
- Make a copy of the file doc\doc.build.user.tmpl and rename that copy to
doc\doc.build.user. Then adjust the paths in that file according to your
setup. You need to edit this file if your installed version of Tortoise has a different
working-copy database version than the tool expects.
- Unzip (if necessary) and copy the font files into %WINDIR%\Fonts.
You will need them only if you are building the respective language packs.
- run 'nant init' to fetch and unzip the required tools. Note: you need to call vcvars32.bat first.
\section build32 Building 32 bit packages
Hint: before you can start building TortoiseSVN, you need to call the vcvars32.bat
file which is located in C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build.
Now, if you got some time left you can run the build script to compile
TortoiseSVN. Grab a cup of coffee, depending on how fast your computer is!
TortoiseSVN build can take advantage of multi-core machines.
Note: if you set the Visual Studio tools for win32, you can not build the
64-bit version of TortoiseSVN. Trying to use the 'x64' nant target will
result in a build error.
To build the 64-bit version, you have to call the 64-bit Visual Studio tools.
And with the 64-bit tools, you can not build the 32-bit version of TortoiseSVN.
Basically: you need to set up the corresponding Visual Studio tools for the build.
\verbatim
> nant
\endverbatim
will show you some help about the targets you can use
\verbatim
> nant setup
\endverbatim
will compile everything, including docs and language packs and create the msi installer
If you encounter any build errors, you can run nant again like this:
\verbatim
> nant setup -l:buildlog.txt
\endverbatim
which will create a build log file which you can use to analyze where
exactly the build failed.
If you need to build only the Subversion libraries:
\verbatim
> nant Subversion
\endverbatim
\section build64cross Building 64 bit packages on win32 (cross-compile)
First, we build some 32-bit SVN utilities you will need later
during the build process. Follow the instructions above or just
open "Microsoft Visual Studio 2017" -> "Visual Studio Tools" ->
"Visual Studio 2017 Command Prompt", change to the TortoiseSVN source
directory and run
\verbatim
> nant binaries
\endverbatim
Now, build the x64 packages: Open
"Microsoft Visual Studio 2017" -> "Visual Studio Tools" ->
"Visual Studio 2017 x64 Cross Tools Command Prompt", change to the
TortoiseSVN source directory and run
\verbatim
> nant x64 cross setup
\endverbatim
After the script finished, the packages can be found in bin.
\section build64 Building 64 bit packages on x64
To build native packages on your 64 bit Windows, just open
"Microsoft Visual Studio 2017" -> "Visual Studio Tools" ->
"Visual Studio 2017 Win64 Command Prompt", change to the
TortoiseSVN source directory and run
Note that to build the x64 msi file, you also have to build the
win32 version of TortoiseSVN first since the x64 msi includes
the win32 version of the shell extension.
\verbatim
> nant x64 setup
\endverbatim
After the script finished, the packages can be found in bin.
\section clean Cleaning the build directories
To clean the files you just built, open a command prompt as explained
above, change to the TortoiseSVN source directory and run
\verbatim
> nant clean
\endverbatim
You will find that Language\Tortoise.pot gets deleted when running the 'clean' target,
which is normal behavior. This generated file is present in the repository so
the translators don't need to execute the entire build if they only wish to
update documentation.
\section buildhelp Learning the current build options
Many other settings can be used. You can see a description of the available nant targets
by running
\verbatim
> nant help
\endverbatim
*/