Menu

[r505]: / trunk / build.txt  Maximize  Restore  History

Download this file

54 lines (37 with data), 2.0 kB

 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
First, you need to install the compiler package.
- You need VS.NET2008
If you want to build the msi make sure the "Tools for Redistributing
Applications" are installed.
Also, you need the MFC feature pack which contains the tr1 c-runtime
extensions (or the SP1 for VS2008 which contains the feature pack).
Next you need to install some utilities/programs:
- Python 2.4(*) : http://www.python.org/windows/
- Perl : http://www.activestate.com/Products/ActivePerl/
- WiX 3(*) : http://wix.sourceforge.net
- NAnt(*) : http://nant.sourceforge.net
(*) 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!
Now you're almost ready. Only a few more steps to do:
- create a new folder on your harddisk, e.g. SVN.
- Checkout the CommitMonitor sources from the Subversion repository into
SVN\CommitMonitor
- Make a copy of the file default.build.user.tmpl in the CommitMonitor root folder and
rename that copy to default.build.user. Then adjust the paths as mentioned
in that file.
Building packages
Hint: before you can start building CommitMonitor, you need to call the vsvars32.bat
file which is located in %VS90COMNTOOLS%.
> nant
will show you some help about the targets you can use
> nant setup
will compile everything and create the msi installer
> nant Subversion
will build all the libraries required. After that you can open the
.sln file in VS2008 and compile the CommitMonitor there.
Don't forget to also build the debug versions of the libraries:
> nant debug Subversion
If you encounter any build errors, you can run nant again like this:
> nant setup -l:buildlog.txt
which will create a build log file which you can use to analyse where
exactly the build failed.
After the script finished, the packages can be found in .\bin .
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.