#3418: "Launch Script (*.sh)" doesn't work on Windows
--------------------------+----------------------------------
Reporter: kking009 | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.2.3
Component: Default | Version: 7.2.2
Resolution: | Keywords: shell script windows
CPU: Unspecified | Platform: MSWindows 7
--------------------------+----------------------------------
Comment (by hellik):
Replying to [comment:3 hellik]:
> Replying to [comment:2 kking009]:
> > On V6.X Grass-Shell-Script were working Cross-Platform! I suppose
Grass were handling them and they weren't dispatched to the OS.
> > If I copy/execute line by line my script to the Grass-Comamnd-Console,
Grass is able to "handle" my scripts.
>
> I mean it more generally,shell scripts aren't working on all operating
systems out of the box, unless you bundle extra bins with the software
(e.g. msys in winGRASS).
>
> IIRC There is a GRASS_SHELL variable to set (have a look in manual and
wiki), but it's not really maintained anymore to have shell script support
in winGRASS 7, as python is all around on the most is.
in the [https://grass.osgeo.org/grass73/manuals/variables.html manual]:
{{{
GRASS_SH
[shell scripts on Windows]
path to bourne shell interpreter used to run shell scripts.
}}}
this variable can be set in the winGRASS startup batch file by e.g.
{{{
set GRASS_SH="C:\OSGeo4W64\apps\msys\bin\sh.exe"
}}}
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3418#comment:5>
GRASS GIS <https://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
