future of GRASS with cygwin

3 messages Options
Embed this post
Permalink
rthompson1743

future of GRASS with cygwin

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)

Hello GRASS users,

                I am not clear on the future of cygwin with GRASS. Is this version being replaced by the native Windows version? If so, how is scripting being done?

Thanks.

Rick


_______________________________________________
grass-windows mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-windows
Markus Neteler

Re: future of GRASS with cygwin

Reply Threaded More More options
Print post
Permalink
Hello Rick,

On Thu, May 14, 2009 at 10:25 PM, Rick Thompson <[hidden email]> wrote:
> Hello GRASS users,
>
>                 I am not clear on the future of cygwin with GRASS. Is this
> version being replaced by the native Windows version? If so, how is
> scripting being done?

General comment:
GRASS is a voluntary project - we (have to) rely on community contributions
to prepare binary packages unless a buildbot or likewise exists to
generate multiple versions.

In this list are hundreds of subscribers - it would be great to find a volunteer
to generate Cygwin-GRASS.

Future of scripting:
In GRASS 6 most scripts are shell scripts, optionally Python scripts
can be used.
In GRASS 7 most scripts are Python scripts, optionally shell scripts
can be used.

The aim is to replace the hardly portable shell scripts with the way more
advanced and portable Python language. Since SWIG is used, also other
language bindings could be generated.

Best
Markus
_______________________________________________
grass-windows mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-windows
Glynn Clements

Re: future of GRASS with cygwin

Reply Threaded More More options
Print post
Permalink
In reply to this post by rthompson1743

Rick Thompson wrote:

> I am not clear on the future of cygwin with GRASS. Is this
> version being replaced by the native Windows version?

No. I expect to produce a Cygwin binary package when 6.4.0 is
released.

Unlike the native Windows version, which requires a fair amount of
code changes, the Cygwin version is just a matter of compiling the
code for Cygwin. Cygwin is a lot closer to Linux than MacOSX is.

> If so, how is scripting being done?

You can script GRASS commands in any language. For 6.4, the native
Windows version uses the MSys bash port to run the provided scripts.
In 7.0, all shell scripts are being replaced with equivalent Python
scripts.

--
Glynn Clements <[hidden email]>
_______________________________________________
grass-windows mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-windows