[GRASS-user] Problems with GRASS python code in osgeo4w

[Hamish]

Bob Moskovitz:
> I noticed that most of the *.bat files have forward slashes.
>  For example:
>
> C:\OSGeo4W\apps\grass\bin\grass64.bat:                 set WINGISBASE=/c/OSGeo4W/apps/grass/grass-6.4.0RC4
> C:\OSGeo4W\apps\grass\grass-6.4.0svn\bin\d.correlate.bat:    @"%GRASS_SH%" -c '"%GISBASE%/scripts/d.correlate" %*'
> C:\OSGeo4W\apps\grass\grass-6.4.0svn\etc\Init.bat:        if "%GRASS_PROJSHARE%"=="" set GRASS_PROJSHARE=/c/OSGeo4W/share/proj
> C:\OSGeo4W\bin\grass64.bat                        set WINGISBASE=%OSGEO4W_ROOT%/apps/grass/grass-6.4.0svn
> 
> Why is there 2 grass64.bat?

osgeo4w actually ships with 3: (!)

C:\OSGeo4W\apps\grass\bin\grass64(.sh) and grass64.bat  (unused)
  https://trac.osgeo.org/osgeo4w/ticket/73
  https://trac.osgeo.org/osgeo4w/ticket/90

C:\OSGeo4W\etc\ini\grass.bat  (sets enviro vars like GRASS_WISH)
  https://trac.osgeo.org/osgeo4w/ticket/86

C:\OSGeo4W\bin\grass64.bat  (and grass64.bat.tmpl)
  this is what is used to actually launch grass


Glynn:
> The rest of them are wrong.
> I didn't realise that the problems with OSGeo4W were this bad.

note what he listed above are from an unused script with OSGeo4W.
(but are used in the stand-alone installer)

things seem to work, e.g. the r.out.xyz shell script works
both from the DOS prompt and the wxGui.


> I suggest that you use the standalone GRASS packages rather than
> OSGeo4W.

if nothing else, the OSGeo4W package is rather old now (6.4svn from 4 May '9)

> Or at least report OSGeo4W-specific problems to the OSGeo4W
> list or tracker.

[except for the 3x grass.bat scripts stuff] note that in general
the stand-alone installer is built out of the osgeo4w tree &
vice versa. they're almost the same thing - at least they share
a lot.

e.g. see mswindows/osgeo4w/ in the grass source code for wxNviz
and wxVdigit linking stuff.

see https://trac.osgeo.org/osgeo4w/wiki/pkg-grass#PackagerNotes
 for partial build method.


Hamish