[GRASS-dev] scripts don't launch GUI from the msys command line
in winGRASS
Markus Neteler
neteler at osgeo.org
Fri Feb 5 07:20:23 EST 2010
On Thu, Feb 4, 2010 at 9:16 PM, Glynn Clements <glynn at gclements.plus.com> wrote:
>
> Helmut Kudrnovsky wrote:
>
>> >So far, I've only seen this in Vista and am wondering if anyone else has seen it. Using the nightly build from 2 February.
>> >
>> >From the command line, type the name of a script, like r.blend, without arguments
>> >Instead of the GUI popping up, there is an error complaining about the lack of arguments.
>> >
>> >It's like g.parser is not being invoked.
>>
>> i can confirm this changed behaviour, typing a command without arguments and no GUI popping up.
>>
>> tested on WinVista32 with self compiled Grass64 and Grass65
>
> Note that if GRASS_GUI is tcltk, it won't work, due to G_popen() not
> working at all on Windows (execl() works like on Unix, i.e. it doesn't
> return if it succeeds; but unlike Unix, Windows doesn't have fork()).
>
> Using the new G_popen() from 7.0 is one option.
... another backport project?
Markus
More information about the grass-dev
mailing list