#1052: Build of 7.0.SVN dont work
---------------------------+------------------------------------------------
Reporter: jeleniste | Owner: martinl
Type: defect | Status: assigned
Priority: normal | Milestone: 7.0.0
Component: Packaging | Version: svn-trunk
Resolution: | Keywords: wingrass
Platform: MSWindows XP | Cpu: x86-32
---------------------------+------------------------------------------------
Comment (by hellik):
Replying to [comment:10 glynn]:
> Replying to [comment:9 martinl]:
> > > subprocess.call() is fine, but SHELL isn't normally going to be set
on Windows, so it will need to be set in a batch file prior to running the
grass70.py script (or the script needs -cmd and -sh options to choose the
shell).
> >
> > what about {{{GRASS_SH}}}
>
> GRASS_SH specifies the program used to run Bourne shell scripts. I don't
know if it's still needed in 7.0, but if it is, it must refer to a
compatible shell regardless of whether you want to use sh.exe or cmd.exe
for the interactive command line.
>
> On Unix, SHELL specifies the user's preferred shell (from the last field
in /etc/passwd). It's meant for use by programs which provide an option to
spawn an interactive shell (e.g. "M-x shell" in Emacs). It will always be
set for an interactive login unless the user explicitly unsets it.
>
> On Windows, the shortcuts need to refer to batch files which set it
explicitly before invoking grass70.py, i.e. "set SHELL=...\bin\sh.exe" for
"start with MSys" and "set SHELL=%COMSPEC%" for "start with Windows
command prompt". Alternatively, extending the grass70.py script with e.g.
-sh and -cmd switches would eliminate the need for batch files and allow
the shortcut to refer to the script directly (AFAIK, a shortcut can
specify arguments but not environment variables).
at the moment, with the desktop-shortcut "GRASS 7.0.SVN" and the "GRASS
Command Line"-shortcut in the program menue
(seehttp://trac.osgeo.org/grass/browser/grass/trunk/mswindows/GRASS-
Installer.nsi#L621)
you get in both cases a windows-commandline with the following
information:
{{{
This version running through: shell (C:\Program Files\GRASS-70-
SVN\msys\bin\sh.exe)
}}}
In this windows-commandline a shell is running and you have access to the
shell-utilities:
i.e.
{{{
GRASS 7.0.svn> gawk --help
Usage: gawk [POSIX or GNU style options] -f progfile [--] file ...
Usage: gawk [POSIX or GNU style options] [--] 'program' file ...
POSIX options: GNU long options:
-f progfile --file=progfile
-F fs --field-separator=fs
-v var=val --assign=var=val
[...]
}}}
And also the windows-commandline commands are working.
So you have both a working shell and a working windows command line.
The only thing is, that you have only access to the following folders in
the moment:
{{{
GRASS 7.0.svn> ls
bin doc etc home info lib m.ico man msys.bat msys.bat.tmpl
msys.ico
}}}
So maybe, we should remove "GRASS 7.0.SVN with MSYS", because there is
already a shell and a windows-commandline accessible.
Helmut
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1052#comment:11>
GRASS GIS <http://grass.osgeo.org>
Currently the