[winGRASS] Re: [GRASS-user] Re: Xganim errors in WinGRASS

GRASS GRASS user
1

Glynn,

I am currently actively using winGRASS for my work because I could not afford the ridiculously expensive suit like the ArcGIS Desktop. I have tried ArcGIS demo and with GRASS and winGRASS current ability has already surpassed ArcGIS Desktop in some areas. I would also like to find out 'How To' and 'How Easy' we can extend winGRASS, in terms of adding functionalities, whether it is the interface/menu functions, or algorithms used to solve let say, network analysis problem.

1. use the native version on a day-to-day basis, in spite of its
current "alpha" quality, and
2. take responsibility for getting any issues resolved.

Point #2 doesn't necessarily mean that they need to fix any and all
bugs themselves, but they will need to provide meaningful bug reports,
apply and test any proposed fixes, etc.

I am more than happy to be part of the group to continuously providing bugs but as for testing fixes I am afraid with my humble (none!) knowledge on C and linux and software building and compiling, I could not help much. Having said that, I would be happy to help if members are willing to provide explanation on the detail steps involves in testing fixes in window terms, i.e. they do not really need to explain everything on the fixes / codes, just the steps on what/where/how to compile and test.

Thanks

Best Regards
Casey

From: Glynn Clements <glynn@gclements.plus.com>
To: Moritz Lennert <mlennert@club.worldonline.be>
CC: grassuser@grass.itc.it, Hamish <hamish_nospam@yahoo.com>, wingrass@grass.itc.it
Subject: Re: [winGRASS] Re: [GRASS-user] Re: Xganim errors in WinGRASS
Date: Thu, 8 Feb 2007 10:37:57 +0000

Moritz Lennert wrote:

> > (general call for packagers)
> > It would sure be nice if someone produced a GRASS 6.2.1 Cygwin binary.
> > Currently the most up-to-date binary available for the Cygwin version
> > is 6.1-cvs April 17, 2006. i.e. there is still no stable GRASS 6.2
> > available for Windows users -- what's the problem? shared libs?
>
> I think this is mainly due to the fact that we are not very far from a
> real native windows version. I think dev efforts should rather be put
> into that.

Actually, I'd say that we're still quite a long way from having a
*usable* native Windows version.

Most of the people who have contributed to the native version don't
normally use Windows[1]. Thus, they aren't likely to be as motivated
to solve issues as would someone who actually has a *need* for a
native Windows version.

[1] At least, not for GRASS; I use it for playing games, watching
videos, and running an X server so that I can do "work" on my Linux
box without needing a second monitor/keyboard.

A *usable* native Windows version is going to require one or more
people who are willing to:

1. use the native version on a day-to-day basis, in spite of its
current "alpha" quality, and
2. take responsibility for getting any issues resolved.

Point #2 doesn't necessarily mean that they need to fix any and all
bugs themselves, but they will need to provide meaningful bug reports,
apply and test any proposed fixes, etc.

Oh, we also need either a version of v.digit which doesn't require an
interactive monitor (XDRIVER), or a port of the driver code (and the
corresponding part of libraster) to Windows. Regarding the latter,
it's the startup code from lib/driver/main.c which is the main issue;
the X-specific stuff is already adequately handled by libW11.

--
Glynn Clements <glynn@gclements.plus.com>

_______________________________________________
winGRASS mailing list
winGRASS@grass.itc.it
http://grass.itc.it/mailman/listinfo/wingrass

_________________________________________________________________
MSN Hotmail is evolving – check out the new Windows Live Mail http://ideas.live.com

2

yuri bay wrote:

I am currently actively using winGRASS for my work because I could not
afford the ridiculously expensive suit like the ArcGIS Desktop. I have
tried ArcGIS demo and with GRASS and winGRASS current ability has already
surpassed ArcGIS Desktop in some areas. I would also like to find out 'How
To' and 'How Easy' we can extend winGRASS, in terms of adding
functionalities, whether it is the interface/menu functions, or algorithms
used to solve let say, network analysis problem.

Note that we already have a usable Windows version using Cygwin (and
there's no real reason why that version can't include xganim; it's
just that the person who built the binary package didn't enable Motif
support, which xganim requires).

It's the "native" Windows version which is currently still at an
"experimental" stage. Once it's "ready", the native version should be
a better option for most users, as Cygwin has problems of its own.

--
Glynn Clements <glynn@gclements.plus.com>

3

Glynn Clements wrote:

Note that we already have a usable Windows version using Cygwin
(and there's no real reason why that version can't include xganim;
it's just that the person who built the binary package didn't enable
Motif support, which xganim requires).

It's the "native" Windows version which is currently still at an
"experimental" stage. Once it's "ready", the native version should be
a better option for most users, as Cygwin has problems of its own.

.. there is no usable 6.2.x cygwin binary; if someone understands how to
compile GRASS for cygwin, chances are they already have access to a UNIX
machine somewhere already. For everyone else on windows there's a choice
between an out of date development snapshot build for cygwin, and the
experimental MSys development snapshot build ..

noisy,
Hamish

4

Hamish wrote:

> Note that we already have a usable Windows version using Cygwin
> (and there's no real reason why that version can't include xganim;
> it's just that the person who built the binary package didn't enable
> Motif support, which xganim requires).
>
> It's the "native" Windows version which is currently still at an
> "experimental" stage. Once it's "ready", the native version should be
> a better option for most users, as Cygwin has problems of its own.

.. there is no usable 6.2.x cygwin binary; if someone understands how to
compile GRASS for cygwin, chances are they already have access to a UNIX
machine somewhere already. For everyone else on windows there's a choice
between an out of date development snapshot build for cygwin, and the
experimental MSys development snapshot build ..

I managed to compile 6.2.1 (using DLLs) on the current version of
Cygwin without any detectable problems (other than that I forgot to
use the Unix/X11 Tcl/Tk, so NVIZ doesn't work).

Once I've recompiled with a working version of NVIZ, I can provide the
resulting binary package if someone tells me how to upload it.

--
Glynn Clements <glynn@gclements.plus.com>

5

On Fri, Feb 09, 2007 at 02:50:53PM +0000, Glynn Clements wrote:
...

I managed to compile 6.2.1 (using DLLs) on the current version of
Cygwin without any detectable problems (other than that I forgot to
use the Unix/X11 Tcl/Tk, so NVIZ doesn't work).

Once I've recompiled with a working version of NVIZ, I can provide the
resulting binary package if someone tells me how to upload it.

Glynn,

for security reasons I no longer have the FTP site here with upload.
If you could store it somewhere, I will fetch it and put onto the
GRASS site.

Markus

6

On Fri, Feb 09, 2007 at 02:50:53PM +0000, Glynn Clements wrote:

Hamish wrote:

...

> .. there is no usable 6.2.x cygwin binary; if someone understands how to
> compile GRASS for cygwin, chances are they already have access to a UNIX
> machine somewhere already. For everyone else on windows there's a choice
> between an out of date development snapshot build for cygwin, and the
> experimental MSys development snapshot build ..

I managed to compile 6.2.1 (using DLLs) on the current version of
Cygwin without any detectable problems (other than that I forgot to
use the Unix/X11 Tcl/Tk, so NVIZ doesn't work).

Once I've recompiled with a working version of NVIZ, I can provide the
resulting binary package if someone tells me how to upload it.

Thanks to Glynn, we now have a new GRASS 6.2.1 winGRASS/Cygwin binary
packages available at
http://grass.itc.it/grass62/binary/mswindows/
(on the mirrors the next 1-2 days)

For now I have linked to Huidae's install instructions. If anyone
provides me with new install docs, I can upload them to the server, too.

Markus

7

Thanks very much for this!!! I hope it inspires a GRASS Windows community
that could take this over.

Michael

On 2/10/07 6:09 AM, "Markus Neteler" <neteler@itc.it> wrote:

On Fri, Feb 09, 2007 at 02:50:53PM +0000, Glynn Clements wrote:

Hamish wrote:

...

.. there is no usable 6.2.x cygwin binary; if someone understands how to
compile GRASS for cygwin, chances are they already have access to a UNIX
machine somewhere already. For everyone else on windows there's a choice
between an out of date development snapshot build for cygwin, and the
experimental MSys development snapshot build ..

I managed to compile 6.2.1 (using DLLs) on the current version of
Cygwin without any detectable problems (other than that I forgot to
use the Unix/X11 Tcl/Tk, so NVIZ doesn't work).

Once I've recompiled with a working version of NVIZ, I can provide the
resulting binary package if someone tells me how to upload it.

Thanks to Glynn, we now have a new GRASS 6.2.1 winGRASS/Cygwin binary
packages available at
http://grass.itc.it/grass62/binary/mswindows/
(on the mirrors the next 1-2 days)

For now I have linked to Huidae's install instructions. If anyone
provides me with new install docs, I can upload them to the server, too.

Markus

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

8

Markus Neteler wrote:

> > .. there is no usable 6.2.x cygwin binary; if someone understands how to
> > compile GRASS for cygwin, chances are they already have access to a UNIX
> > machine somewhere already. For everyone else on windows there's a choice
> > between an out of date development snapshot build for cygwin, and the
> > experimental MSys development snapshot build ..
>
> I managed to compile 6.2.1 (using DLLs) on the current version of
> Cygwin without any detectable problems (other than that I forgot to
> use the Unix/X11 Tcl/Tk, so NVIZ doesn't work).
>
> Once I've recompiled with a working version of NVIZ, I can provide the
> resulting binary package if someone tells me how to upload it.

Thanks to Glynn, we now have a new GRASS 6.2.1 winGRASS/Cygwin binary
packages available at
http://grass.itc.it/grass62/binary/mswindows/
(on the mirrors the next 1-2 days)

For now I have linked to Huidae's install instructions. If anyone
provides me with new install docs, I can upload them to the server, too.

The package I made is just a .tar.gz file. It should be extracted into
Cygwin's root directory, e.g.:

  $ cd /
  $ tar xzf /path/to/grass-6.2.1-cygwin.tar.gz

Everything will be /usr/local/grass-6.2.1, except for the grass62
script which is in /usr/local/bin.

Regarding external dependencies: the only dependencies which aren't
provided by Cygwin are GDAL and Tcl/Tk.

I used the tcltk-grass package from Huidae's site, so you'll probably
need the same package if you want to run NVIZ (NVIZ itself is
statically linked, but it will probably still need the scripts in
/usr/local/lib/tcl8.4 and tk8.4).

GDAL is 1.3.1, built from source. Again, that's statically linked;
certain things will need GDAL's "share" directory, although that's
likely to be less version-specific than is the case for Tcl/Tk. If
necessary, I can provide the GDAL 1.3.1 binaries (3.8 MiB).

As for using Cygwin's setup.exe, I suspect that a similar process to
that described on Huidae's site could be made to work for grass.itc.it
by adding a suitable setup.ini file to the same directory as the
tarball; see:

  http://geni.ath.cx/grass/setup.ini

I don't think that you need anything except the setup.ini and the
tarballs (which are just normal tarballs designed to extract into the
root directory).

--
Glynn Clements <glynn@gclements.plus.com>

9

Glynn,

I have a running GRASS-6.1 cvs 8 (from Huidae's compilation) on cygwin. I
installed your version, could not find a gdal-1.3.1 as you used, but the
new 1.4. It compiled fine, is installed. GRASS-6.1 still starts, works
fine (as far as I can see so far). But the GRASS-6.2.1 starts the start
dialogs, but opening an existing location/mapset crashes it. Trying to
generate a new location from the GUI fails, as it tries to place it under
'//<path-to-database>. So I generated a new location under the correct
path with the text based dialog. GRASS 6.2.1 starts now, but the gis.m
does not work. The splash screen opens, and what looks like the base gis.m
window, but it immediately crashes with 'child process exited abnormally'.
Any hints what is missing or where I can start to search for more clues?
I'm a bit rusty with compiling, but with a few hints I should be able to
get it going and test it.

Cheers for compiling,

Arne

Markus Neteler wrote:

> > .. there is no usable 6.2.x cygwin binary; if someone understands
how to
> > compile GRASS for cygwin, chances are they already have access to a
UNIX
> > machine somewhere already. For everyone else on windows there's a
choice
> > between an out of date development snapshot build for cygwin, and
the
> > experimental MSys development snapshot build ..
>
> I managed to compile 6.2.1 (using DLLs) on the current version of
> Cygwin without any detectable problems (other than that I forgot to
> use the Unix/X11 Tcl/Tk, so NVIZ doesn't work).
>
> Once I've recompiled with a working version of NVIZ, I can provide the
> resulting binary package if someone tells me how to upload it.

Thanks to Glynn, we now have a new GRASS 6.2.1 winGRASS/Cygwin binary
packages available at
http://grass.itc.it/grass62/binary/mswindows/
(on the mirrors the next 1-2 days)

For now I have linked to Huidae's install instructions. If anyone
provides me with new install docs, I can upload them to the server, too.

The package I made is just a .tar.gz file. It should be extracted into
Cygwin's root directory, e.g.:

  $ cd /
  $ tar xzf /path/to/grass-6.2.1-cygwin.tar.gz

Everything will be /usr/local/grass-6.2.1, except for the grass62
script which is in /usr/local/bin.

Regarding external dependencies: the only dependencies which aren't
provided by Cygwin are GDAL and Tcl/Tk.

I used the tcltk-grass package from Huidae's site, so you'll probably
need the same package if you want to run NVIZ (NVIZ itself is
statically linked, but it will probably still need the scripts in
/usr/local/lib/tcl8.4 and tk8.4).

GDAL is 1.3.1, built from source. Again, that's statically linked;
certain things will need GDAL's "share" directory, although that's
likely to be less version-specific than is the case for Tcl/Tk. If
necessary, I can provide the GDAL 1.3.1 binaries (3.8 MiB).

As for using Cygwin's setup.exe, I suspect that a similar process to
that described on Huidae's site could be made to work for grass.itc.it
by adding a suitable setup.ini file to the same directory as the
tarball; see:

  http://geni.ath.cx/grass/setup.ini

I don't think that you need anything except the setup.ini and the
tarballs (which are just normal tarballs designed to extract into the
root directory).

--
Glynn Clements <glynn@gclements.plus.com>

_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser

10

pallentina@niwa.co.nz wrote:

I have a running GRASS-6.1 cvs 8 (from Huidae's compilation) on cygwin. I
installed your version, could not find a gdal-1.3.1 as you used, but the
new 1.4. It compiled fine, is installed. GRASS-6.1 still starts, works
fine (as far as I can see so far). But the GRASS-6.2.1 starts the start
dialogs, but opening an existing location/mapset crashes it. Trying to
generate a new location from the GUI fails, as it tries to place it under
'//<path-to-database>. So I generated a new location under the correct
path with the text based dialog. GRASS 6.2.1 starts now, but the gis.m
does not work. The splash screen opens, and what looks like the base gis.m
window, but it immediately crashes with 'child process exited abnormally'.

With 'child process exited abnormally' errors, it's necessary to know
which program it was trying to run.

Any hints what is missing or where I can start to search for more clues?
I'm a bit rusty with compiling, but with a few hints I should be able to
get it going and test it.

Contrary to my earlier statements, GDAL is actually a DLL (I had
forgotten that Windows libraries typically consist of both a DLL and a
corresponding static library). Hopefully I can get Markus to put the
GDAL package on the GRASS web site at some point. I wouldn't invest
too much effort into tracking down problems using a different version
of GDAL.

--
Glynn Clements <glynn@gclements.plus.com>

11

Hi,

Do I need to uninstall my current winGRASS native binary version if I want to install the 6.2 Cygwin winGRASS?

Thanks

Casey

From: Glynn Clements <glynn@gclements.plus.com>
To: pallentina@niwa.co.nz
CC: grassuser@grass.itc.it, wingrass@grass.itc.it
Subject: Re: [GRASS-user] GRASS GIS 6.2.1 winGRASS/Cygwin binaries available: was: Re: Xganim errors in WinGRASS
Date: Sun, 11 Feb 2007 17:52:10 +0000

pallentina@niwa.co.nz wrote:

> I have a running GRASS-6.1 cvs 8 (from Huidae's compilation) on cygwin. I
> installed your version, could not find a gdal-1.3.1 as you used, but the
> new 1.4. It compiled fine, is installed. GRASS-6.1 still starts, works
> fine (as far as I can see so far). But the GRASS-6.2.1 starts the start
> dialogs, but opening an existing location/mapset crashes it. Trying to
> generate a new location from the GUI fails, as it tries to place it under
> '//<path-to-database>. So I generated a new location under the correct
> path with the text based dialog. GRASS 6.2.1 starts now, but the gis.m
> does not work. The splash screen opens, and what looks like the base gis.m
> window, but it immediately crashes with 'child process exited abnormally'.

With 'child process exited abnormally' errors, it's necessary to know
which program it was trying to run.

> Any hints what is missing or where I can start to search for more clues?
> I'm a bit rusty with compiling, but with a few hints I should be able to
> get it going and test it.

Contrary to my earlier statements, GDAL is actually a DLL (I had
forgotten that Windows libraries typically consist of both a DLL and a
corresponding static library). Hopefully I can get Markus to put the
GDAL package on the GRASS web site at some point. I wouldn't invest
too much effort into tracking down problems using a different version
of GDAL.

--
Glynn Clements <glynn@gclements.plus.com>

_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser

_________________________________________________________________
MSN Hotmail is evolving – check out the new Windows Live Mail http://ideas.live.com

12

yuri bay wrote:

Do I need to uninstall my current winGRASS native binary version if I want
to install the 6.2 Cygwin winGRASS?

No.

--
Glynn Clements <glynn@gclements.plus.com>

13

On Sun, 11 Feb 2007, yuri bay wrote:

Hi,

Do I need to uninstall my current winGRASS native binary version if I want to install the 6.2 Cygwin winGRASS?

I would say probably not, as long as you make sure there are no MinGW or Msys directories left over in your PATH environment variable - the Cygwin versions of the Unix-style utilities should be the only ones accessible when you're using Cygwin. I think when you start the Cygwin shell it inherits the Windows PATH - so just make sure there is no Mingw or Msys stuff in there. If you want to use the Msys GRASS again you could change the PATH if necessary.

Paul

14

Hi All,
having a setup.exe as it is for GRASS6.1 would be very welcome.
When can we expect thi pl.
Greetings
Ravi Kumar

Markus Neteler neteler@itc.it wrote:

On Fri, Feb 09, 2007 at 02:50:53PM +0000, Glynn Clements wrote:

Hamish wrote:
…

… there is no usable 6.2.x cygwin binary; if someone understands how to
compile GRASS for cygwin, chances are they already have access to a UNIX
machine somewhere already. For everyone else on windows there’s a choice
between an out of date development snapshot build for cygwin, and the
experimental MSys development snapshot build …

I managed to compile 6.2.1 (using DLLs) on the current version of
Cygwin without any detectable problems (other than that I forgot to
use the Unix/X11 Tcl/Tk, so NVIZ doesn’t work).

Once I’ve recompiled with a working version of NVIZ, I can provide the
resulting binary package if someone tells me how to upload it.

Thanks to Glynn, we now have a new GRASS 6.2.1 winGRASS/Cygwin binary
packages available at
http://grass.itc.it/grass62/binary/mswindows/
(on the mirrors the next 1-2 days)

For now I have linked to Huidae’s install instructions. If anyone
provides me with new install docs, I can upload them to the server, too.

Markus

grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser

Have a burning question? Go to Yahoo! Answers and get answers from real people who know.

15

Markus wrote:

> Thanks to Glynn, we now have a new GRASS 6.2.1 winGRASS/Cygwin
> binary packages available at
> http://grass.itc.it/grass62/binary/mswindows/
> (on the mirrors the next 1-2 days)

just curious:

Were these built with or without PostgreSQL support? SQLite? Other
goodies?

thanks,
Hamish

16

Hamish wrote:

> > Thanks to Glynn, we now have a new GRASS 6.2.1 winGRASS/Cygwin
> > binary packages available at
> > http://grass.itc.it/grass62/binary/mswindows/
> > (on the mirrors the next 1-2 days)

just curious:

Were these built with or without PostgreSQL support? SQLite? Other
goodies?

Built without PostgreSQL, then the PostgreSQL driver built separately.

Although, is that still necessary? NVIZ doesn't appear to have a
direct libpq dependency any more.

In any case, the only thing which requires libpq is the "pg" driver.

--
Glynn Clements <glynn@gclements.plus.com>

17

RAVI KUMAR wrote:

  having a setup.exe as it is for GRASS6.1 would be very welcome.
  When can we expect thi pl.

You can install it using Cygwin's setup program, using a variation on
Huidae's instructions at:

  http://geni.ath.cx/grass.html#toc5

I'm not sure there's much point providing a stand-alone installer, as
you would still have to install Cygwin itself using its setup program.

--
Glynn Clements <glynn@gclements.plus.com>

18

Dear Glynn,

I have encountered the following error when I first time invoked the Cygwin winGRASS 6.2 after I have successfully installed it. I am using both native binary and the new cygwin 6.2 winGRASS. I have copy and past my GRASSDATA dir into cygwin directory so that I can access the same data using cygwin winGRASS. But when I have selected the correct directory and mapset, the following error occured on the xwindow:

GRASS 6.2.1 (L_UK):~ > child process exited abnormally, by using gis.m on the xwin will give the same error.

L_UK is my mapset, what could have cause this error, your help is much appreciated.

Thanks

Casey Wong

From: Glynn Clements <glynn@gclements.plus.com>
To: "yuri bay" <ksh_wong@msn.com>
CC: grassuser@grass.itc.it, wingrass@grass.itc.it
Subject: Re: [winGRASS] Re: Need uninstall native winGRASS for 6.2 CygwinwinGRASS??
Date: Sun, 11 Feb 2007 20:30:19 +0000

yuri bay wrote:

> Do I need to uninstall my current winGRASS native binary version if I want
> to install the 6.2 Cygwin winGRASS?

No.

--
Glynn Clements <glynn@gclements.plus.com>

_________________________________________________________________
Have you tried Windows Live Spaces? Tell us what you think! https://www.msnfeedback.com/perseus/surveys/961278308/6653c632.htm

19

yuri bay wrote:

I have encountered the following error when I first time invoked the
Cygwin winGRASS 6.2 after I have successfully installed it. I am
using both native binary and the new cygwin 6.2 winGRASS. I have
copy and past my GRASSDATA dir into cygwin directory so that I can
access the same data using cygwin winGRASS. But when I have selected
the correct directory and mapset, the following error occured on the
xwindow:

GRASS 6.2.1 (L_UK):~ > child process exited abnormally, by using gis.m
on the xwin will give the same error.

what does it say if you type "g.region -p" at that prompt?

"d.mon x0" ?
"gis.m" ?

Hamish

20

To Hamish and everyone,

From: Hamish <hamish_nospam@yahoo.com>
To: "yuri bay" <ksh_wong@msn.com>
CC: grassuser@grass.itc.it, wingrass@grass.itc.it
Subject: Re: [GRASS-user] Re: Cygwin winGRASS 6.2 errors
Date: Tue, 13 Feb 2007 12:34:17 +1300

yuri bay wrote:
>
> I have encountered the following error when I first time invoked the
> Cygwin winGRASS 6.2 after I have successfully installed it. I am
> using both native binary and the new cygwin 6.2 winGRASS. I have
> copy and past my GRASSDATA dir into cygwin directory so that I can
> access the same data using cygwin winGRASS. But when I have selected
> the correct directory and mapset, the following error occured on the
> xwindow:
>
> GRASS 6.2.1 (L_UK):~ > child process exited abnormally, by using gis.m
> on the xwin will give the same error.

what does it say if you type "g.region -p" at that prompt?

"d.mon x0" ?
"gis.m" ?

With gis.m or "gis.m" the results are the same, child process exited abnormally
With d.mon x0, a monitor is activated.
With g.region -p, there is no respond or error

and for all the child process errors shown on the Xwindow, the errors shown in the Cygwin command prompt is:

winMultiWindowxMsgProcErrorHandler - Error: Badwindow (invalid Window parameter)

What seem to be the problem?? why can I open a mapset within a location in the grass_data directory when they are properly configured?

Any help is much appreciated.

Regards
Casey Wong

_________________________________________________________________
Click Here To Find Your Perfect Match This Valentines! http://msnuk.match.com/