[GRASS-user] GRASS for windows script solution

[francesco]

Yep, I tried that, but gave me a strange result reading the 
C:\xxx\yyy and turning it into /xxx/yyy without the "C" part - I had 
to add it using the /c/xxx/yyy syntax directly:  maybe I was doing 
something wrong.
Good idea to add it in the grass63.bat file though, to avoid touching 
the init.bat.  I will try that!

Thank you Moritz.

Francesco Pirotti

At 11.38 28/11/2007, Moritz Lennert wrote:
>On 28/11/07 11:01, francesco wrote:
>>Hello,
>>For all fearless Wingrass users,  I would like to share a solution 
>>for the following bug  ...."many shell scripts do not work, even if 
>>you enable correctly msys and include LIB and BIN paths in the PATH 
>>windows variable............" (from the readme file at the wingrass webpage).
>>PROBLEM - Long story short, g.mlist gave me errors because it did 
>>not fine "sed" and other executables, therefore scripts like 
>>g.mlist and g.mremove do not work
>>SOLUTION -
>>    1 - open the "Init.bat" file located in the 
>> "<grassinstallationdirectory>/grass-6.3.xxx/*etc*" ... do not use 
>> notepad but a better editor that recognizes unix formatted text
>>    2 - add the line below *after* the   ..........if not 
>> "%GRASS_ADDON_PATH%"==...................... line (should be line 29)
>>           set PATH=/c/msys/1.0/bin;%PATH%
>>    3 - of course /c/msys/1.0/bin is the path to the bin directory 
>> of msys, if yours is different, adapt.
>>    4 - start grass and try.
>
>As mentioned int he README: "in order for shell scripts to work, you 
>will have to add msys' lib and bin directories to your path in the 
>grass63.bat file."
>
>So, no need to fiddle with Init.bat, just add it in grass63.bat:
>
>set PATH=%PATH+;c:\msys\1.0\bin;c:\msys\1.0\lib
>
>The information used to be in the .bat file, but we decided to take 
>it out in the effort of making wingrass independent of msys. But 
>seeing the many reactions on this, I think I will add it again.
>
>Moritz
>