[GRASS-dev] Re: winGRASS

[Paul Kelly]

Oh and in case anybody is trying this, you won't get too far with the 
Windows startup without changing the path to WINGISBASE in grass63.bat 
(the startup file) to have Windows-style backslash-\ directory separator 
characters. Can't seem to get the Makefile to put these in but I guess 
I'll get it working eventually.

On Tue, 12 Dec 2006, Paul Kelly wrote:

> Hello Moritz
> I've got a bit further with documenting what I was doing. See attached for 
> some of my notes. Mostly on compiling the accompanying libraries GRASS 
> absolutely needs:
> XDR
> Zlib
> libpng
> PROJ.4
> GDAL
>
> I put these into a gzipped tar file in case anybody would like to get started 
> quickly - in this case you would just need Msys,Mingw with bison and flex. 
> Everything else included in here:
> http://www.stjohnspoint.co.uk/grass/wingrass-extralibs.tar.gz
> and then the prefix where you untar that file you will need to supply to the 
> GRASS configure as:
> --with-includes=prefix --with-libs=prefix
> FWIW my configure line was:
> ./configure --prefix=c:/grass --bindir=c:/grass/bin \
> --with-includes=/c/grass/forgrass/include \
> --with-libs=/c/grass/forgrass/lib --with-cxx --without-jpeg --without-tiff \
> --without-postgres --with-opengl=windows --without-fftw --without-x \
> --enable-x11=no --enable-shared=yes --with-tcltk-includes=/c/tcl/include \
> --with-tcltk-libs=/c/tcl/bin
>
> After compiling you should copy libxdr.dll, libproj.dll, libpng.dll, 
> libgdal-1.dll and libz.dll.1.2.3 into the GRASS lib directory and all the 
> GDAL and PROJ .exe files in the bin directory into the GRASS bin directory, 
> and then you have a more or less self-contained GRASS distribution.
>
> I also installed Activestate Tcl/Tk 8.4.13 (in c:\tcl).
>
> I could make a binary distribution that sort of works OK to a certain extent 
> without having Msys/Mingw installed, only thing is I want to wait until Nviz 
> is working again on Windows as it was up to yesterday. The problem is 
> starting it from a script. Scripts are very problematic (and of course only 
> possible at all if you have Msys installed) because of the way Msys handles 
> Windows paths.
>
> If you have Msys and Mingw installed, putting their bin directories in the 
> PATH makes things in general run more smoothly, but of course that's 
> cheating!
>
> Paul
>