Hi
I have just uninstalled Binary version and installed GRASS from OSGEO4W. Script files work just fine.
I tried to install r.out.kml with g.extension but I got this error:
which: svn: unknown command
ERROR: svn client required. Please install Subversion first.
(maybe it is relevant to indicate that in the help file and a few links to Subversion clients)
Nevertheless, I added the script file into script folder, html to manual page and created a r.out.kml.bat in bin folder and it worked.
Bes regards,
Antonio Rocha
--
António Rocha
Earth Observation Applications and Services
Av. D. João II, Lt 1.17.01 - 10º, Ed. Torre Zen
1998-023 Lisboa, Portugal
Ph: +351 21 893 30 23
Fax: +351 21 896 90 99 http://www.deimos.pt
I tried to install r.out.kml with g.extension but I got this error:
which: svn: unknown command
ERROR: svn client required. Please install Subversion first.
(maybe it is relevant to indicate that in the help file and a few links to
Subversion clients)
have you tried to install extension from command line or wxGUI [1]?
wxGUI uses another g.extension (Python based) which should download on
Windows directly prepared binaries.
Hello Martin
I tried from the command line in the GUI.
Ok next time I will give a try with that extension. Thanks
On 13-09-2012 10:40, Martin Landa wrote:
I tried to install r.out.kml with g.extension but I got this error:
which: svn: unknown command
ERROR: svn client required. Please install Subversion first.
(maybe it is relevant to indicate that in the help file and a few links to
Subversion clients)
have you tried to install extension from command line or wxGUI [1]?
wxGUI uses another g.extension (Python based) which should download on
Windows directly prepared binaries.
--
António Rocha
Earth Observation Applications and Services
Av. D. João II, Lt 1.17.01 - 10º, Ed. Torre Zen
1998-023 Lisboa, Portugal
Ph: +351 21 893 30 23
Fax: +351 21 896 90 99 http://www.deimos.pt
On Thu, Sep 13, 2012 at 11:40 AM, Martin Landa <landa.martin@gmail.com> wrote:
...
have you tried to install extension from command line or wxGUI [1]?
wxGUI uses another g.extension (Python based) which should download on
Windows directly prepared binaries.
I wonder if the command line bash shell g.extension could be redicted
*on Windows* to
the Python based g.extension to avoid these problems?
I wonder if the command line bash shell g.extension could be redicted
*on Windows* to the Python based g.extension to avoid these problems?
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 get really frustrated by software that assumes it knows better and locks
out otherwise possible things, so I try not to replicate that behaviour...
As it is anecdotally quite rare for Windows users to have that full
build-from-source environment (most download the pre-built .exe installer)
if it does remain, I would think it good to add a WARNING for Windows
command line users to try it from the GUI instead. (and so download
pre-built parcels from Martin's site) e.g. for the debian/ubuntu packages
g.extension(.*) returns a non-fatal warning if the -dev package isn't
installed too, which says "what you are trying to do probably won't work,
this is why, and this is how to fix it".
On Fri, Sep 14, 2012 at 5:57 AM, Hamish <hamish_b@yahoo.com> wrote:
Markus N:
I wonder if the command line bash shell g.extension could be redicted
*on Windows* to the Python based g.extension to avoid these problems?
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...
It will not work for most of them ever.
Hence we tell them to use the wxGUI and voilà it works for most.
I get really frustrated by software that assumes it knows better and locks
out otherwise possible things, so I try not to replicate that behaviour...
Most winGRASS users get frustrated to be mislead here.
As it is anecdotally quite rare for Windows users to have that full
build-from-source environment (most download the pre-built .exe installer)
if it does remain, I would think it good to add a WARNING for Windows
command line users to try it from the GUI instead.
Yes, this is the minimum we can do.
Or just get it done automatically: if no gcc present, switch to the
Python script.
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.