>> I purposely left the g.extension(.sh) installed in the Windows build as >> theoretically & fundamentally it should work if the user has a full >> compiler >> and build environment for grass set up. For those people, and in the hope >> that someone might be able to make it work better someday, it remains. > >I tend to disagree - most (99%?) of our Windows users will not have >a compiler environment installed. Just browse the archives how many >failed into the trap of using g.extension on Windows on command line... [...] >Yes, this is the minimum we can do. >Or just get it done automatically: if no gcc present, switch to the >Python script.
AFAIK the standalone wingrass-installer has an build/compiler environment inside, because it's based upon the osgeo4w-build-stack; but there are whitespace-in-path-issues related to gcc etc. "normal" osgeo4w-wingrass-users probably hasn't installed the build-deps by default. >This should be urgently fixed. +1 ----- best regards Helmut -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Using-r-out-kml-and-scripts-in-Windows-Binary-error-tp5001496p5001913.html Sent from the Grass - Users mailing list archive at Nabble.com. _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user