Difference between revisions of "WinGRASS 6 Current Status"

From GRASS-Wiki
Jump to navigation Jump to search
(→‎Vista: +win7 missing dll problem)
Line 222: Line 222:

[[Category: Development]]
[[Category: Development]]
[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse phone lookup]
[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

Revision as of 20:58, 30 December 2011

See also http://trac.osgeo.org/grass/wiki/BuildingOnWindows

This page describes the current status of winGRASS development:

  • Older precompiled winGRASS/Cygwin packages are available for GRASS 6.3,
  • Older native winGRASS packages GRASS 6.3,

Current status - Summary

The native windows port of GRASS is slowly coming to a stage where it can be considered mature beta status. All main functions seem to work, but much more testing is needed. The port is of the current SVN release branch for GRASS 6.4.0. The only prior native port of an earlier version is 6.3.0.

The general idea is to reach a point where GRASS runs in MS-Windows without any kind of UNIX emulation. Currently this is possible but limits the use to compiled modules, as scripts are all of UNIX-shell type and cannot run within a Windows cmd.exe environment without a series of UNIX tools such as a shell, awk, sed, etc. So in order to run such scripts a collection of UNIX-like tools needs to be installed, such as Msys or Gnuwin32+Shell.

Another major feature not available in the MS-Windows version are the old-style interactive X monitors (i.e. the x0, PNG, PS, Cairo, etc, monitors opened with 'd.mon x0'). Only direct rendering works currently. Display is thus "limited" to the Tcl/Tk and wxPython GUIs (the latter might still need some cleanup of UNIX-specific code). Modules like i.points and d.zoom will not work due to their interactive monitor requirements (see #Known_Issues).

Installing binary snapshots

Regular binary snapshots for windows are available from the main GRASS download page.

Compiling by yourself


All informations for compiling yourself are in Compiling GRASS on MS-Windows

Nullsoft installer

See http://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/mswindows

New winGRASS installer 1 New winGRASS installer 2 New winGRASS installer 3

Known Issues

See also


  • wxVdigit (vector digitizer) doesn't work. see trac #541.
Workaround: Use the old Tcl/Tk v.digit module, simply type v.digit at the Cmd> prompt in the Layer Manager GUI.
Please test the new wxNviz on Windows and report any issues. For a workaround: Use the Tcl/Tk nviz module, simply type nviz at the terminal prompt in shell window.
  • Spaces in path names
    • Installation directory: WinGRASS uses the MSys software to run on MS-Windows. Unfortunately MSys isn't very interested in supporting spaces in path names, but WinGrass-development in the last few months tried to get this ready. Currently the default installation directory is c:\Programm Files\Grass-64\
    • GIS data directory: It is generally safe to have spaces in your GIS data directory path, but there are few spots where it might still get confused and chop the path off at the first space. If you find one please report it to the bug tracker, the sooner we know about it the sooner we can fix it.
Workaround: if this is causing problems for you the quick solution is to rename the GIS data directory and replace all spaces with underscores (_).
  • The r.li suite and d.mon monitors won't work. These use UNIX pipes and won't work on Windows without a lot of work.

Won't fix (at least not immediately)

Issues listed here are rather impossible to fix due to the different nature of native Windows. Or, lend us a hand and let's try harder!

  • No monitors

This means that you cannot launch any monitor launched with d.mon (x0, PNG, PS, etc). The only way you can render is directly to a file. But you cannot directly display to screen from the command line. This will be solved in GRASS 7 with a new rendering system and possibly via the new wxgrass GUI. So no work will probably be put into this until then.

The absence of monitors also makes impossible the use of interactive modules based on these monitors, such as:

i.points and i.vpoints have already been replaced by the gis.m georectifier module (File -> Georectify). In replacement of i.class you can digitize training areas with v.digit. This will not however, give you all the information i.class provides, such as the histogram of the region, the statistics and the display of matches. These modules will have to be rewritten to clearly separate display and backend parts, so that the backend can be run on the command line or from any GUI frontend. Volunteers needed.

Another module affected is d.vect.thematic which uses monitors. This will hopefully be replaced by a C-version in a not too far future.

  • Scripts need *nix-like shell

All current GRASS 6.4 scripts are written in shell language. This means they need a shell, and several related tools (awk, sed, etc), to function. The actual WinGrass 6.4-installer includes Msys, so all shell-scripts should work.

In 7.0, these scripts have been rewritten in Python, thus totally eliminating the need for any shell.

Platform specific issues


If the GRASS GUI startup fails with "[Error 14001]" in the MSys terminal on a relatively fresh install of XP, the solution is to install some missing DLL files from Microsoft which apparently don't come standard. If these library files are missing, Quantum GIS and other software from the OSGeo4W stack will likely encounter the same trouble as well.

You'll need to install two files: (in order)

  • MS's Windows Installer 3.1 Redistributable (v2)
  • MS's .net framework 3.5 downloader

It is recommended to run Windows updates after installing these.



  • Missing MSVCR71.dll on startup
Try installing Microsoft's .net frameworks as described above in the XP section. If that doesn't solve it, try these instructions found in a web search: http://i.justrealized.com/2009/how-to-fix-missing-msvcr71dll-problem-in-windows/



  • change the Uninstall icon
  • fix the language errors in the StartMenu link's descriptions
  • change the name of the South-Dakota sample database to Spearfish60
  • add a GRASS Command Line link (cmd.exe) into the GRASS StartMenu group
  • create a GRASS Addons installer or integrate the GRASS Addons in the current installer as downloadable options.
See g.extension in GRASS 6.5+


GRASS Dependencies
  • add the Indipendent JPEG support to GRASS *
  • add the FFMPEG support in GRASS (reports an error in building OGSF library; probably needs to specify -lavutil in gcc command) ***
  • add the NLS support in GRASS (needs gettext)
  • add the wxWidgets support in GRASS (for the wxPython GUI v.digit replacement)
GDAL Dependencies
  • add the ECW support in GDAL */**
  • add the JPEG2000 support in GDAL (through Jasper or Kadaku *) **
  • add the OGDI support in GDAL *
  • add the MrSID support in GDAL */**
GRASS and GDAL Dependencies
  • add the Xerces support in both GDAL and GRASS *
  • add the ODBC support in both GDAL and GRASS */**
  • add the MySQL support in both GDAL and GRASS */**
Miscellaneus Dependencies
  • add the OpenSSL support in both PostgreSQL and SQLite *
  • add the AVCE00 tools (build from source in minGW)
  • add the E00compr tools (build from source in minGW)
  • add the GPSBabel tool (use prebuilt binaries from GPSBabel Web Site)

* needs to build related libraries from source in MinGW
** needs to check the licences first
*** FFMPEG has been already succesfully built on MinGW

Internal Libraries

  • parser: find out why launching a module from the command line without parameters does not call module GUI

Vector modules

  • v.in.ascii crashes on files with irregular line length (see this thread)

Raster modules

  • r.terraflow does not compile fix backported 27/3/2008
This seems to be due to the use of the function getrusage() which is not supported under MinGW. Check this octave patch email thread.

Other modules

  • r.li moduels do not compile (they require UNIX sockets, much the same situation as the display monitors)
Use the older r.le modules instead.

GRASS Addons

  • compile the GRASS Addons

TclTk issues


  • metacharacter escape in "sh -c '$cmd'"
  • modules not working: v.neighbors, v.kernel, r.cost
  • Cannot open Help pages.
  • Have to type "exit" in the console to save ~/.grassrc file. Then, close gis.m to finish the session.
  • A previous installation of grass under cygwin is likely to cause problems with WinGrass. Follow the directions to remove cygwin at http://cygwin.com/faq/faq-nochunks.html#faq.setup.uninstall-all

The following items cannot be fixed in the near future:

    • can't read "_data(.gronsole.gronsole,4,donecmd)": no such element in array error
      • Could you be more precise about this error ? When does it occur ?

Dealing with shell scripts or .bat files

Bourne shell scripts require MSys (or some other Bourne shell), but you don't need to start GRASS from MSys.

The main issue with scripts is that Windows doesn't understand the "#!" notation used to specify the interpreter.

All of the supplied scripts in $GISBASE/scripts have a corresponding .bat file in $GISBASE/bin which invokes script via %GRASS_SH%. This allows you to run those scripts from the Windows command prompt.

If you write scripts of your own, you need to either add a corresponding .bat file, or give the script a .sh extension and associate that with the shell, e.g. via the ftype and assoc commands. You can use the PATHEXT variable to eliminate the need to type the extension.

Other libraries


  • lib/gis/OBJ.*/fmode.o is needed for any GRASS related modules.
  • modified ltmain.sh to install binary files from wrapper scripts.
  • see also GDAL Building With MinGW

Related efforts


reverse phone lookup

phone number lookup