Hi Marco,
On 24/01/08 12:22, [EMAIL PROTECTED] wrote:
I built grass-6.3.0RC4 in MinGW and MSYS Enviroment using source code
from
http://download.osgeo.org/grass/grass63/source/grass-6.3.0RC4.tar.gz
<http://mailstore.rossoalice.alice.it/exchweb/bin/redir.asp?URL=http://download.osgeo.org/grass/grass63/source/grass-6.3.0RC4.tar.gz>
Reading the error log I tried to look for the reasons of that errors.
First I checked out /imagery/i.class build errors. It seems to be
Please look at (and amend)
http://grass.gdf-hannover.de/wiki/WinGRASS_Current_Status
Currently, the following i.* modules do not compile (also the info at
http://geog-pc40.ulb.ac.be/grass/wingrass/, notably winmakeerror.log):
/c/grasssrc/grass6/imagery/i.class
/c/grasssrc/grass6/imagery/i.ortho.photo/photo.2image
/c/grasssrc/grass6/imagery/i.ortho.photo/photo.2target
/c/grasssrc/grass6/imagery/i.points
/c/grasssrc/grass6/imagery/i.vpoints
All of these won't work because they interactively use x-monitors which
do not work on Windows (see last night's post by Glynn on that question:
http://lists.osgeo.org/pipermail/grass-dev/2008-January/034965.html).
So, I'm not sure that it is really worth spending any time on trying to
solve compilation problems on them. They should be (and partly are -
i.e. i.points/i.vpoints are replaced by the georectifier in gis.m)
replaced by a combination of non-interactive modules and a gui layer.
However, what would be good to study and solve are the compilation
errors for r.terraflow and r.li*...
Moritz
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
