Hello,
I have updated the GRASS native win package at
http://moritz.homelinux.org/grass/wingrass/
(see instructions in the README file)
We definitely need testers if we want to speed up development on this. I don't have much time to spend on testing at the moment. Even though you can use a variety of modules in winGRASS, we are still far from a really usable port. Only testing (and fixing 
) will get us there.
Moritz
On Fri, May 18, 2007 at 04:18:48PM +0200, Moritz Lennert wrote:
Hello,
I have updated the GRASS native win package at
http://moritz.homelinux.org/grass/wingrass/
(see instructions in the README file)
We definitely need testers if we want to speed up development on this. I
don't have much time to spend on testing at the moment. Even though you
can use a variety of modules in winGRASS, we are still far from a really
usable port. Only testing (and fixing
Moritz has posted the remaining compile errors at
http://moritz.homelinux.org/grass/wingrass/winmakerrors.log
Especially this is of interest to be fixed:
/c/grasssrc/grass6/raster/r.li/r.li.daemon
gcc -shared -o /c/grasssrc/grass6/dist.i686-pc-mingw32/lib/liblibr_li.6.3.cvs.dll -L/c/grasssrc/grass6/dist.i686-pc-mingw32/lib -Wl,--export-dynamic,--enable-runtime-pseudo-reloc -L/c/grasslibs/lib -L/c/Programme/PostgreSQL/8.2/lib OBJ.i686-pc-mingw32/daemon.o OBJ.i686-pc-mingw32/list.o OBJ.i686-pc-mingw32/ipc.o OBJ.i686-pc-mingw32/worker.o OBJ.i686-pc-mingw32/GenericCell.o OBJ.i686-pc-mingw32/avl.o OBJ.i686-pc-mingw32/avlID.o -lgrass_gis -lgrass_datetime -lxdr -liberty -lws2_32 -lz && \
(cd /c/grasssrc/grass6/dist.i686-pc-mingw32/lib; ln -f -s liblibr_li.6.3.cvs.dll /c/grasssrc/grass6/dist.i686-pc-mingw32/lib/liblibr_li.dll)
OBJ.i686-pc-mingw32/daemon.o: In function `calculateIndex':c:/grasssrc/grass6/raster/r.li/r.li.daemon/daemon.c:58: undefined reference to `mkfifo'
:c:/grasssrc/grass6/raster/r.li/r.li.daemon/daemon.c:71: undefined reference to `mkfifo'
:c:/grasssrc/grass6/raster/r.li/r.li.daemon/daemon.c:73: undefined reference to `fork'
:c:/grasssrc/grass6/raster/r.li/r.li.daemon/daemon.c:217: undefined reference to `wait'
:c:/grasssrc/grass6/raster/r.li/r.li.daemon/daemon.c:218: undefined reference to `WIFEXITED'
:c:/grasssrc/grass6/raster/r.li/r.li.daemon/daemon.c:237: undefined reference to `wait'
:c:/grasssrc/grass6/raster/r.li/r.li.daemon/daemon.c:238: undefined reference to `WIFEXITED'
collect2: ld returned 1 exit status
Markus
On Fri, May 18, 2007 at 06:31:04PM +0200, Markus Neteler wrote:
On Fri, May 18, 2007 at 04:18:48PM +0200, Moritz Lennert wrote:
> Hello,
>
> I have updated the GRASS native win package at
>
> http://moritz.homelinux.org/grass/wingrass/
>
> (see instructions in the README file)
Hi,
here at ISESS2007 (Prague), we have just made a successful test on
MS Vista.
Few observations:
- grass63.bat should be in DOS encoding (we had to change the path
since Vista doesn't want stuff installed in c:\ )
- the "help" buttons don't work in the gis.m (maybe known)
- DBF access failed (r.to.vect in our case; this we really need to fix)
Besides this we did a couple of watershed calculations etc.
Markus
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Markus Neteler ha scritto:
- DBF access failed (r.to.vect in our case; this we really need to fix)
could this be related to the problems encountered by windows users with
qgis+grass?
pc
- --
Paolo Cavallini
http://www.faunalia.it/pc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGVbCq/NedwLUzIr4RAidDAJ98kKmwcXZ+hPGr00+BZROGJkILKwCfZ9NQ
aAnGstCaLNi3an7Eqfd+Dy8=
=4g3c
-----END PGP SIGNATURE-----
On 24/05/07 17:35, Paolo Cavallini wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Markus Neteler ha scritto:
- DBF access failed (r.to.vect in our case; this we really need to fix)
Could you be a bit more specific about what failed how ?
could this be related to the problems encountered by windows users with
qgis+grass?
Possibly. Could you point me to any relevant bug reports or similar ?
Moritz
On Thu, May 24, 2007 at 06:10:46PM +0200, Moritz Lennert wrote:
On 24/05/07 17:35, Paolo Cavallini wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>
>
>Markus Neteler ha scritto:
>
>>- DBF access failed (r.to.vect in our case; this we really need to fix)Could you be a bit more specific about what failed how ?
They wanted to use r.to.vect to convert [r.]watershed basins to
vector polygons. Doing so, r.to.vect was whining about DBF. I don't
have the detailed error message since it wasn't my machine - sorry.
Maybe you/someone could try r.watershed + r.to.vect?
>could this be related to the problems encountered by windows users with
>qgis+grass?Possibly. Could you point me to any relevant bug reports or similar ?
Moritz
http://blog.qgis.org/?q=node/71
contains a report from Benjamin.
Markus
On 24/05/07 18:36, Markus Neteler wrote:
On Thu, May 24, 2007 at 06:10:46PM +0200, Moritz Lennert wrote:
On 24/05/07 17:35, Paolo Cavallini wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Markus Neteler ha scritto:
- DBF access failed (r.to.vect in our case; this we really need to fix)
Could you be a bit more specific about what failed how ?
They wanted to use r.to.vect to convert [r.]watershed basins to
vector polygons. Doing so, r.to.vect was whining about DBF. I don't
have the detailed error message since it wasn't my machine - sorry.
Maybe you/someone could try r.watershed + r.to.vect?
r.watershed elevation=elevation.dem@PERMANENT threshold=100 basin=basins stream=streams half.basin=half_basins visual=watershed_vis
r.to.vect input=streams@user1 output=streams feature=line
works perfectly for me.
The same for
r.to.vect input=basinsuser1 output=basins feature=area
If you (or the people who did the tests) can provide more details, I could try again.
Moritz
On 25/05/07 10:44, Moritz Lennert wrote:
r.watershed elevation=elevation.dem@PERMANENT threshold=100 basin=basins stream=streams half.basin=half_basins visual=watershed_vis
What is strange, however, is that when I run this command from the GUI, a terminal window opens showing the progress percentages in text and not the nice progress bar in the Output window of the GIS Manager.
Any idea why ?
Moritz
On Fri, 25 May 2007, Moritz Lennert wrote:
On 25/05/07 10:44, Moritz Lennert wrote:
r.watershed elevation=elevation.dem@PERMANENT threshold=100 basin=basins stream=streams half.basin=half_basins visual=watershed_vis
What is strange, however, is that when I run this command from the GUI, a terminal window opens showing the progress percentages in text and not the nice progress bar in the Output window of the GIS Manager.
Any idea why ?
I'd guess it is because the r.watershed binary is only really a wrapper to parse the options and it calls other helper programs to actually do the work, and these are the ones that output the progress information. I suppose it could be a system()/G_spawn() issue. I guess the spawned process needs to inherit the setting that tells it it should output progress information in the GUI-compatible format (is there an environment variable that tells it that?) and also that stderr of the spawned process needs to be going to the same place as that of the original r.watershed process so the GUI can pick it up and turn it into a progress bar. Probably quite complicated - at least it works at the minute.
Paul
No idea off the top of my head. Has this behavior changed in recent weeks?
In late April, I made some changes to the progress bar routines in gronsole
because GRASS would crash when a medium fast (not instantaneous nor slow)
command would try to report its progress via a progress bar. It seemed to
fix the problem and should have had no other side effects. But I suppose
this could be one. You could slot in a version of gronsole.tcl prior to the
end of April and see what happens.
Michael
On 5/25/07 1:49 AM, "Moritz Lennert" <mlennert@club.worldonline.be> wrote:
On 25/05/07 10:44, Moritz Lennert wrote:
r.watershed elevation=elevation.dem@PERMANENT threshold=100 basin=basins
stream=streams half.basin=half_basins visual=watershed_visWhat is strange, however, is that when I run this command from the GUI,
a terminal window opens showing the progress percentages in text and not
the nice progress bar in the Output window of the GIS Manager.Any idea why ?
Moritz
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
Aha!
Michael
On 5/25/07 3:53 AM, "Paul Kelly" <paul-grass@stjohnspoint.co.uk> wrote:
On Fri, 25 May 2007, Moritz Lennert wrote:
On 25/05/07 10:44, Moritz Lennert wrote:
r.watershed elevation=elevation.dem@PERMANENT threshold=100 basin=basins
stream=streams half.basin=half_basins visual=watershed_visWhat is strange, however, is that when I run this command from the GUI, a
terminal window opens showing the progress percentages in text and not the
nice progress bar in the Output window of the GIS Manager.Any idea why ?
I'd guess it is because the r.watershed binary is only really a wrapper to
parse the options and it calls other helper programs to actually do the
work, and these are the ones that output the progress information. I
suppose it could be a system()/G_spawn() issue. I guess the spawned
process needs to inherit the setting that tells it it should output
progress information in the GUI-compatible format (is there an environment
variable that tells it that?) and also that stderr of the spawned process
needs to be going to the same place as that of the original r.watershed
process so the GUI can pick it up and turn it into a progress bar.
Probably quite complicated - at least it works at the minute.Paul
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
Moritz Lennert wrote on 05/25/2007 10:44 AM:
On 24/05/07 18:36, Markus Neteler wrote:
On Thu, May 24, 2007 at 06:10:46PM +0200, Moritz Lennert wrote:
On 24/05/07 17:35, Paolo Cavallini wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Markus Neteler ha scritto:
- DBF access failed (r.to.vect in our case; this we really need to
fix)Could you be a bit more specific about what failed how ?
They wanted to use r.to.vect to convert [r.]watershed basins to
vector polygons. Doing so, r.to.vect was whining about DBF. I don't
have the detailed error message since it wasn't my machine - sorry.
Maybe you/someone could try r.watershed + r.to.vect?r.watershed elevation=elevation.dem@PERMANENT threshold=100
basin=basins stream=streams half.basin=half_basins visual=watershed_visr.to.vect input=streams@user1 output=streams feature=line
works perfectly for me.
The same for
r.to.vect input=basinsuser1 output=basins feature=area
If you (or the people who did the tests) can provide more details, I
could try again.Moritz
_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev
------------------
ITC -> dall'1 marzo 2007 Fondazione Bruno Kessler
ITC -> since 1 March 2007 Fondazione Bruno Kessler
------------------
Moritz Lennert wrote on 05/25/2007 10:44 AM:
On 24/05/07 18:36, Markus Neteler wrote:
On Thu, May 24, 2007 at 06:10:46PM +0200, Moritz Lennert wrote:
On 24/05/07 17:35, Paolo Cavallini wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Markus Neteler ha scritto:
- DBF access failed (r.to.vect in our case; this we really need to
fix)Could you be a bit more specific about what failed how ?
They wanted to use r.to.vect to convert [r.]watershed basins to
vector polygons. Doing so, r.to.vect was whining about DBF. I don't
have the detailed error message since it wasn't my machine - sorry.
Maybe you/someone could try r.watershed + r.to.vect?r.watershed elevation=elevation.dem@PERMANENT threshold=100
basin=basins stream=streams half.basin=half_basins visual=watershed_visr.to.vect input=streams@user1 output=streams feature=line
works perfectly for me.
The same for
r.to.vect input=basinsuser1 output=basins feature=area
If you (or the people who did the tests) can provide more details, I
could try again.
The person doing the testing is probably already on a different
continent now 
I remember (now) that they used "gis.m" to do r.watershed and r.to.vect.
Now I have no longer access to MS-Vista.
Markus
------------------
ITC -> dall'1 marzo 2007 Fondazione Bruno Kessler
ITC -> since 1 March 2007 Fondazione Bruno Kessler
------------------
On 28/05/07 18:24, Markus Neteler wrote:
Moritz Lennert wrote on 05/25/2007 10:44 AM:
On 24/05/07 18:36, Markus Neteler wrote:
On Thu, May 24, 2007 at 06:10:46PM +0200, Moritz Lennert wrote:
On 24/05/07 17:35, Paolo Cavallini wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Markus Neteler ha scritto:
- DBF access failed (r.to.vect in our case; this we really need to
fix)Could you be a bit more specific about what failed how ?
They wanted to use r.to.vect to convert [r.]watershed basins to
vector polygons. Doing so, r.to.vect was whining about DBF. I don't
have the detailed error message since it wasn't my machine - sorry.
Maybe you/someone could try r.watershed + r.to.vect?r.watershed elevation=elevation.dem@PERMANENT threshold=100
basin=basins stream=streams half.basin=half_basins visual=watershed_visr.to.vect input=streams@user1 output=streams feature=line
works perfectly for me.
The same for
r.to.vect input=basinsuser1 output=basins feature=area
If you (or the people who did the tests) can provide more details, I
could try again.The person doing the testing is probably already on a different
continent now
I remember (now) that they used "gis.m" to do r.watershed and r.to.vect.
Same here.
Now I have no longer access to MS-Vista.
Neither do I...
Moritz