Hi,
when following
https://trac.osgeo.org/grass/wiki/CompileOnWindows#CompilingandInstallingGRASS6.4.0
(i.e., running ./mswindows/osgeo4w/package.sh with MinGW):
GRASS is compiled, HTML manual is built etc. Then it installs (tar xBf ...),
(man/ is skipped), then "STARTING cleanup", and then
"STARTING building vc libraries"
??
Then it fails with
mswindows/osgeo4w/mklibs.sh: dumpbin: command not found
I wonder why it tries to use VC stuff here. Is it for the QGIS interface?
If so, what's the trick here? If Visual Studio is needed, shouldn't it be
mentioned in the install instructions?
confused,
Markus
For the record VC is required to build some parts of the grass osgeo4w
packages. jef included this in the script so that others could update
the packages for the osgeo4w installer.
If I remember correctly, jef and I both tried to get everything made
in MinGW but a few things wouldn't work so VC had to be used in the
end.
hellik's update to comment out those lines is perfect but we shouldn't
remove them entirely.
-Colin
On 19 January 2010 01:52, Markus Neteler <neteler@osgeo.org> wrote:
Hi,
when following
https://trac.osgeo.org/grass/wiki/CompileOnWindows#CompilingandInstallingGRASS6.4.0
(i.e., running ./mswindows/osgeo4w/package.sh with MinGW):
GRASS is compiled, HTML manual is built etc. Then it installs (tar xBf ...),
(man/ is skipped), then "STARTING cleanup", and then
"STARTING building vc libraries"
??
Then it fails with
mswindows/osgeo4w/mklibs.sh: dumpbin: command not found
I wonder why it tries to use VC stuff here. Is it for the QGIS interface?
If so, what's the trick here? If Visual Studio is needed, shouldn't it be
mentioned in the install instructions?
confused,
Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev