[GRASS-dev] Re: [GRASS GIS] #580: WinGRASS:
$GISBASE/etc/gui/scripts/ require something like $(EXE) to run
GRASS GIS
trac at osgeo.org
Fri Jan 6 09:03:53 EST 2012
#580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run
---------------------------+------------------------------------------------
Reporter: hamish | Owner: grass-dev@…
Type: defect | Status: reopened
Priority: blocker | Milestone: 7.0.0
Component: wxGUI | Version: svn-trunk
Resolution: | Keywords: wingrass
Platform: MSWindows XP | Cpu: Unspecified
---------------------------+------------------------------------------------
Comment(by hellik):
Replying to [comment:35 martinl]:
> Replying to [comment:34 mmetz]:
> > Reopening the ticket because calling python scripts from /scripts with
wxGUI does not work with the error message that the system does not know
what to do with py files. This applies to systems without a separate
system-wide python 2.x installation. Or is a separate python 2.x
installation now a requirement?
> >
> > Example: Settings -> Install extensions from add-ons fails.
>
> This should be fixed in trunk. Probably we could introduce bat-files for
python scripts as in G6 for bash-scripts. I tried `bin\g.manual.bat`
>
> {{{
> @"%GRASS_PYTHON%" "%GISBASE%/scripts/g.manual.py" %*
> }}}
>
> from CLI
>
> {{{
> g.manual
> command not found
>
> g.manual.bat
> line 1: @%GRASS_PYTHON%: command not found
> }}}
>
> Any idea?
>
>
>
I've tried some time ago
g.manual.py.bat,
as the bat-filename, it worked.
Helmut
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/580#comment:36>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list