Send grass-windows mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.osgeo.org/mailman/listinfo/grass-windows
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of grass-windows digest..."
Today's Topics:
1. Re: native grass63RC4 and MSYS shell (Glynn Clements)
2. Re: native grass63RC4 and MSYS shell (Moritz Lennert)
3. Re: native grass63RC4 and MSYS shell (Mirko Baruffini)
----------------------------------------------------------------------
Message: 1
Date: Mon, 11 Feb 2008 19:43:03 +0000
From: Glynn Clements <[EMAIL PROTECTED]>
Subject: Re: [GRASS-windows] native grass63RC4 and MSYS shell
To: Moritz Lennert <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Moritz Lennert wrote:
> > AFAIK, starting GRASS or running GRASS commands from the MSys shell is
> > unsupported under Windows.
>
> No, it should work. I cannot reproduce the above error messages.
> However, to make the current 63RC4 package work, you have to change the
> bin/grass63 file from
>
> GISBASE=c:/grass63RC4/grass-6.3.0RC4
>
> to
>
> GISBASE=/c/grass63RC4/grass-6.3.0RC4
>
> Then it works well for me (not everything tested, though).
>
> > Unfortunately, MSys shell provides an environment which is somewhere
> > between Unix and Windows, and not entirely compatible with either. In
> > particular, any pathnames which GRASS sees will need to be compatible
> > with Windows, e.g. C:\path\to\file or C:/path/to/file rather than
> > MSys' /c/path/to/file convention.
>
> Well, actually, as you can see above, for launching grass you need the
> msys style.
Shell scripts need MSys-style paths. If you're lucky, the shell will
convert the paths to Windows format when running a Windows binary.
Internally, WinGRASS requires valid Windows paths.
MSys usually handles this conversion for command-line arguments and
some environment variables, but not when writing data to files (e.g.
you can end up with an MSys-style path for GISDBASE in $GISRC, and
then everything fails).
> > The focus of WinGRASS is to produce a *native* Windows version. Unless
> > you're building WinGRASS yourself, you shouldn't need MSys for
> > anything other than running shell scripts.
>
> And even then, I guess other shells would also do the trick, such as
> Gnuwin32's shell and tools such as awk and sed. Msys is more convenient
> as the default installation contains these tools.
The issue is that all shells invariably include some form of Unix
emulation which has to be undone before the data can be passed on to
Windows functions. Sometimes the shell manages to do this
automatically, sometimes it doesn't. If it doesn't, you have to
perform the conversion yourself.
--
Glynn Clements <[EMAIL PROTECTED]>
------------------------------
Message: 2
Date: Mon, 11 Feb 2008 20:26:53 +0100
From: Moritz Lennert <[EMAIL PROTECTED]>
Subject: Re: [GRASS-windows] native grass63RC4 and MSYS shell
To: Mirko Baruffini <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 11/02/08 16:39, Mirko Baruffini wrote:
>
> Thank you Moritz!
> Now it works! I have modified the file bin/grass63 as you told me. But
> the scipts run only in text mode....
> Can I also run them with a GUI?
> Can you help me?
What does not work in the GUI ? Do you get error messages ?
Moritz
>
> Mirko
>
>
> Moritz Lennert ha scritto:
>> On 08/02/08 22:11, Glynn Clements wrote:
>>> Mirko Baruffini wrote:
>>>
>>>> I' m using wingrass grass63RC4. The use is ok, but, when I launch
>>>> grass63.bat, it does not load the shell msys (I have uncommented and
>>>> adapted some of the environment variables in grass/bin/grass63.bat).
>>>>
>>>> So i decided to launch a script with native wingrass launching grass
>>>> from within the msys shell.
>>>> When I type /c/grass/bin/grass63 it does not load grass. On the
>>>> sceen I can read:
>>>>
>>>> [EMAIL PROTECTED] /
>>>> $ /c/grass63RC4/bin/grass63
>>>> /c/grass63RC4/grass-6.3.0RC4/etc/Init.sh: uname: command not found
>>>> /c/grass63RC4/grass-6.3.0RC4/etc/Init.sh: uname: command not found
>>>> /c/grass63RC4/grass-6.3.0RC4/etc/Init.sh: mkdir: command not found
>>>> Cannot create temporary directory! Exiting.
>>>>
>>>> But the command uname exists:
>>>>
>>>> [EMAIL PROTECTED] /
>>>> $ uname
>>>> MINGW32_NT-5.1
>>>>
>>>> What could I do?
>>>
>>> AFAIK, starting GRASS or running GRASS commands from the MSys shell is
>>> unsupported under Windows.
>>
>> No, it should work. I cannot reproduce the above error messages.
>> However, to make the current 63RC4 package work, you have to change
>> the bin/grass63 file from
>>
>> GISBASE=c:/grass63RC4/grass-6.3.0RC4
>>
>> to
>>
>> GISBASE=/c/grass63RC4/grass-6.3.0RC4
>>
>> Then it works well for me (not everything tested, though).
>>
>>> Unfortunately, MSys shell provides an environment which is somewhere
>>> between Unix and Windows, and not entirely compatible with either. In
>>> particular, any pathnames which GRASS sees will need to be compatible
>>> with Windows, e.g. C:\path\to\file or C:/path/to/file rather than
>>> MSys' /c/path/to/file convention.
>>
>> Well, actually, as you can see above, for launching grass you need the
>> msys style.
>>
>>> The focus of WinGRASS is to produce a *native* Windows version. Unless
>>> you're building WinGRASS yourself, you shouldn't need MSys for
>>> anything other than running shell scripts.
>>
>> And even then, I guess other shells would also do the trick, such as
>> Gnuwin32's shell and tools such as awk and sed. Msys is more
>> convenient as the default installation contains these tools.
>>
>> Moritz
>>
>
> _______________________________________________
> grass-windows mailing list
> [email protected]
> http://lists.osgeo.org/mailman/listinfo/grass-windows
------------------------------
Message: 3
Date: Tue, 12 Feb 2008 09:18:38 +0100
From: Mirko Baruffini <[EMAIL PROTECTED]>
Subject: Re: [GRASS-windows] native grass63RC4 and MSYS shell
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
http://lists.osgeo.org/pipermail/grass-windows/attachments/20080212/0dd1153a/attachment-0001.html
------------------------------
_______________________________________________
grass-windows mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-windows
End of grass-windows Digest, Vol 18, Issue 8
********************************************
