@@ -28,10 +28,11 @@ You only need Microsoft Windows Core SDK / Build Environment (x86 32-Bit).
28
28
Download and install following packages:
29
29
30
30
|| Tool | Website |
31
- | CMake | http://www.cmake.org/files/v2.8/cmake-2.8.2 -win32-x86.exe |
31
+ | CMake | http://www.cmake.org/files/v2.8/cmake-2.8.4 -win32-x86.exe |
32
32
| Flex | http://gnuwin32.sourceforge.net/downlinks/flex.php |
33
33
| Bison | http://gnuwin32.sourceforge.net/downlinks/bison.php |
34
34
| SVN | http://sourceforge.net/projects/win32svn/files/1.6.13/Setup-Subversion-1.6.13.msi/download |
35
+ | or GIT | http://msysgit.googlecode.com/files/Git-1.7.4-preview20110204.exe |
35
36
| OSGeo4W | http://download.osgeo.org/osgeo4w/osgeo4w-setup.exe |
36
37
37
38
OSGeo4W does not only provide ready packages for the current QGIS release and
@@ -98,6 +99,12 @@ svn to the source directory ``qgis-trunk``:
98
99
svn co https://svn.osgeo.org/qgis/trunk/qgis qgis-trunk
99
100
```
100
101
102
+ or using git-svn (from the git shell):
103
+
104
+ ```
105
+ git svn clone --username timlinux --revision 15611:HEAD https://svn.osgeo.org/qgis/trunk/qgis
106
+ ```
107
+
101
108
Create a 'build' directory somewhere. This will be where all the build output
102
109
will be generated.
103
110
@@ -152,7 +159,9 @@ creatensis.pl
152
159
```
153
160
154
161
When the script completes, it should have created a QGIS installer executable
155
- in the ms-windows directory.
162
+ in the ms-windows directory. If you want to include your own hand built QGIS
163
+ executables, you need to copy them in from your windows installation into
164
+ the ms-windows file tree created by the creatensis script.
156
165
157
166
=== Osgeo4w packaging ===
158
167
0 commit comments