[GRASS-dev] Unable to install manual for add-on r.estimap.recreation under Windows

Dear Windows experts,

in installing the add-on r.estimap.recreation under Windows, I get this error:

ERROR: Unable to read manual page: [Errno 2] No such file or directory: 'C:\\OSGEO4~1\\apps\\grass\\grass-7.4.4\\docs\\html\\r.estimap.recreation.html'

What can I do about this? Is it an non-clean installation of GRASS GIS
issue?

I've found a couple of old references:

https://lists.osgeo.org/pipermail/grass-dev/2012-November/060651.html
https://lists.osgeo.org/pipermail/grass-user/attachments/20141023/007284ec/attachment.html
https://lists.osgeo.org/pipermail/grass-dev/2015-August/075990.html

Nothing with a specific explanation and solution though.

Nikos

NikosAlexandris wrote

Dear Windows experts,

in installing the add-on r.estimap.recreation under Windows, I get this
error:

ERROR: Unable to read manual page: [Errno 2] No such file or directory:
'C:\\OSGEO4~1\\apps\\grass\\grass-7.4.4\\docs\\html\\r.estimap.recreation.html'

What can I do about this? Is it an non-clean installation of GRASS GIS
issue?

I've found a couple of old references:

https://lists.osgeo.org/pipermail/grass-dev/2012-November/060651.html
https://lists.osgeo.org/pipermail/grass-user/attachments/20141023/007284ec/attachment.html
https://lists.osgeo.org/pipermail/grass-dev/2015-August/075990.html

Nothing with a specific explanation and solution though.

Nikos
_______________________________________________
grass-dev mailing list

grass-dev@.osgeo

https://lists.osgeo.org/mailman/listinfo/grass-dev

see compilation Log:

https://wingrass.fsv.cvut.cz/grass77/x86_64/addons/grass-7.7.svn/logs/r.estimap.recreation.log

the addon isn't compiled, therefore the Message.

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

* Helmut Kudrnovsky <hellik@web.de> [2019-01-13 09:51:25 -0700]:

NikosAlexandris wrote

Dear Windows experts,

in installing the add-on r.estimap.recreation under Windows, I get this
error:

ERROR: Unable to read manual page: [Errno 2] No such file or directory:
'C:\\OSGEO4~1\\apps\\grass\\grass-7.4.4\\docs\\html\\r.estimap.recreation.html'

What can I do about this? Is it an non-clean installation of GRASS GIS
issue?

I've found a couple of old references:

https://lists.osgeo.org/pipermail/grass-dev/2012-November/060651.html
https://lists.osgeo.org/pipermail/grass-user/attachments/20141023/007284ec/attachment.html
https://lists.osgeo.org/pipermail/grass-dev/2015-August/075990.html

Nothing with a specific explanation and solution though.

Nikos
_______________________________________________
grass-dev mailing list

grass-dev@.osgeo

https://lists.osgeo.org/mailman/listinfo/grass-dev

see compilation Log:

https://wingrass.fsv.cvut.cz/grass77/x86_64/addons/grass-7.7.svn/logs/r.estimap.recreation.log

the addon isn't compiled, therefore the Message.

Thanks for heads-up! Now, what's next to check?

if [ "/c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/scripts/r.estimap.recreation.py" != "" ] ; then GISRC=/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/demolocation/.grassrc77 GISBASE=C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32 PATH="/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/scripts:$PATH" PYTHONPATH="C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/etc/python;C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/gui/wxpython;$PYTHONPATH" PATH="/c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/scripts:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/lib:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/lib:/c/osgeo4w64/bin:/c/msys64/usr/bin:/c/msys64/mingw64/bin:/c/ProgramData/Oracle/Java/javapath:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/Microsoft SQL Server/110/Tools/Binn:/c/Program Files/Microsoft Windows Performance Toolkit:/c/Program Files (x86)/Windows Kits/8.1/Windows Performance Toolkit:/c/Program Files (x86)/Git/cmd" LC_ALL=C LANG=C LANGUAGE=C /c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/scripts/r.estimap.recreation.py --html-description < /dev/null | grep -v '</body>\|</html>' > r.estimap.recreation.tmp.html ; fi
/bin/sh: /c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/scripts/r.estimap.recreation.py: /usr/bin/python: bad interpreter: Permission denied
/c/msys64/usr/src/grass_trunk/include/Make/Html.make:14: recipe for target 'r.estimap.recreation.tmp.html' failed

What can I make out of this? Is there something wrong in the HTML file?
(Which I need to update, anyway.) I am searching of course in trac and
else to see how I can go on with this.

Thanks for any help, Nikos

On Sun, Jan 13, 2019 at 7:24 PM Nikos Alexandris
<nik@nikosalexandris.net> wrote:

* Helmut Kudrnovsky <hellik@web.de> [2019-01-13 09:51:25 -0700]:
>NikosAlexandris wrote
>> Dear Windows experts,
>>
>> in installing the add-on r.estimap.recreation under Windows, I get this
>> error:
>>
>> ERROR: Unable to read manual page: [Errno 2] No such file or directory:
>> 'C:\\OSGEO4~1\\apps\\grass\\grass-7.4.4\\docs\\html\\r.estimap.recreation.html'

[..]

>see compilation Log:
>
>https://wingrass.fsv.cvut.cz/grass77/x86_64/addons/grass-7.7.svn/logs/r.estimap.recreation.log
>
>the addon isn't compiled, therefore the Message.

[...]

Thanks for heads-up! Now, what's next to check?

```
if [ "/c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/scripts/r.estimap.recreation.py" != "" ] ; then GISRC=/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/demolocation/.grassrc77 GISBASE=C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32 PATH="/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/scripts:$PATH" PYTHONPATH="C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/etc/python;C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/gui/wxpython;$PYTHONPATH" PATH="/c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/scripts:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/lib:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/lib:/c/osgeo4w64/bin:/c/msys64/usr/bin:/c/msys64/mingw64/bin:/c/ProgramData/Oracle/Java/javapath:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/Microsoft SQL Server/110/Tools/Binn:/c/Program Files/Microsoft Windows Performance Toolkit:/c/Program Files (x86)/Windows Kits/8.1/Windows Performance Toolkit:/c/Program Files (x86)/Git/cmd" LC_ALL=C LANG=C LANGUAGE=C /c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/scripts/r.estimap.recreation.py --html-description < /dev/null | grep -v '</body>\|</html>' > r.estimap.recreation.tmp.html ; fi
/bin/sh: /c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/scripts/r.estimap.recreation.py: /usr/bin/python: bad interpreter: Permission denied

/usr/bin/python: bad interpreter: Permission denied
is a current issue on the Windows server.

Martin may be able to check.

Markus

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-13 19:26:04 +0100]:

* Helmut Kudrnovsky <hellik@web.de> [2019-01-13 09:51:25 -0700]:

NikosAlexandris wrote

Dear Windows experts,

in installing the add-on r.estimap.recreation under Windows, I get this
error:

ERROR: Unable to read manual page: [Errno 2] No such file or directory:
'C:\\OSGEO4~1\\apps\\grass\\grass-7.4.4\\docs\\html\\r.estimap.recreation.html'

What can I do about this? Is it an non-clean installation of GRASS GIS
issue?

I've found a couple of old references:

https://lists.osgeo.org/pipermail/grass-dev/2012-November/060651.html
https://lists.osgeo.org/pipermail/grass-user/attachments/20141023/007284ec/attachment.html
https://lists.osgeo.org/pipermail/grass-dev/2015-August/075990.html

Nothing with a specific explanation and solution though.

Nikos
_______________________________________________
grass-dev mailing list

grass-dev@.osgeo

https://lists.osgeo.org/mailman/listinfo/grass-dev

see compilation Log:

https://wingrass.fsv.cvut.cz/grass77/x86_64/addons/grass-7.7.svn/logs/r.estimap.recreation.log

the addon isn't compiled, therefore the Message.

Thanks for heads-up! Now, what's next to check?

if [ "/c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/scripts/r.estimap.recreation.py" != "" ] ; then GISRC=/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/demolocation/.grassrc77 GISBASE=C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32 PATH="/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/scripts:$PATH" PYTHONPATH="C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/etc/python;C:/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/gui/wxpython;$PYTHONPATH" PATH="/c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/bin:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/scripts:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/lib:/c/msys64/usr/src/grass_trunk/dist.x86_64-w64-mingw32/lib:/c/osgeo4w64/bin:/c/msys64/usr/bin:/c/msys64/mingw64/bin:/c/ProgramData/Oracle/Java/javapath:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/Microsoft SQL Server/110/Tools/Binn:/c/Program Files/Microsoft Windows Performance Toolkit:/c/Program Files (x86)/Windows Kits/8.1/Windows Performance Toolkit:/c/Program Files (x86)/Git/cmd" LC_ALL=C LANG=C LANGUAGE=C /c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/scripts/r.estimap.recreation.py --html-description < /dev/null | grep -v '</body>\|</html>' > r.estimap.recreation.tmp.html ; fi
/bin/sh: /c/Users/landa/grass_packager/grass77/x86_64/addons/r.estimap.recreation/scripts/r.estimap.recreation.py: /usr/bin/python: bad interpreter: Permission denied
/c/msys64/usr/src/grass_trunk/include/Make/Html.make:14: recipe for target 'r.estimap.recreation.tmp.html' failed

What can I make out of this? Is there something wrong in the HTML file?
(Which I need to update, anyway.) I am searching of course in trac and
else to see how I can go on with this.

Is it the shebang line? I.e., it should be

`#!/usr/bin/env python`

instead of

`#!/usr/bin/python` ?

I have to wait till tomorrow for the re-compilation I guess.

Nikos

On Sun, Jan 13, 2019 at 7:41 PM Nikos Alexandris
<nik@nikosalexandris.net> wrote:

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-13 19:26:04 +0100]:
>* Helmut Kudrnovsky <hellik@web.de> [2019-01-13 09:51:25 -0700]:

...

Is it the shebang line? I.e., it should be

`#!/usr/bin/env python`

instead of

`#!/usr/bin/python` ?

Bingo.

ag 'usr/bin/python'
r.estimap.recreation/test.r.estimap.recreation.py
1:#!/usr/bin/python\<nl>\

r.estimap.recreation/r.estimap.recreation.py
1:#!/usr/bin/python

All the other Python scripts use

#!/usr/bin/env python

So that needs to be fixed in your two scripts.

Markus

PS: sorry Martin, for my previous wrong email.

* Markus Neteler <neteler@osgeo.org> [2019-01-13 19:43:10 +0100]:

On Sun, Jan 13, 2019 at 7:41 PM Nikos Alexandris
<nik@nikosalexandris.net> wrote:

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-13 19:26:04 +0100]:
>* Helmut Kudrnovsky <hellik@web.de> [2019-01-13 09:51:25 -0700]:

...

Is it the shebang line? I.e., it should be

`#!/usr/bin/env python`

instead of

`#!/usr/bin/python` ?

Bingo.

ag 'usr/bin/python'
r.estimap.recreation/test.r.estimap.recreation.py
1:#!/usr/bin/python\<nl>\

r.estimap.recreation/r.estimap.recreation.py
1:#!/usr/bin/python

All the other Python scripts use

#!/usr/bin/env python

So that needs to be fixed in your two scripts.

I've updated both. Hope to see it working tomorrow.

N

ps- @Martin and @Helmut and every other person that works on the
MS-Windows front: a HUGE thank you for your efforts. I can only guess
that it must be a hard work to make things roll under Windows.

Hi Nikos,

ne 13. 1. 2019 v 23:29 odesílatel Nikos Alexandris
<nik@nikosalexandris.net> napsal:

ps- @Martin and @Helmut and every other person that works on the
MS-Windows front: a HUGE thank you for your efforts. I can only guess
that it must be a hard work to make things roll under Windows.

you are welcome :slight_smile: Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-13 23:31:26 +0100]:

* Markus Neteler <neteler@osgeo.org> [2019-01-13 19:43:10 +0100]:

On Sun, Jan 13, 2019 at 7:41 PM Nikos Alexandris
<nik@nikosalexandris.net> wrote:

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-13 19:26:04 +0100]:

* Helmut Kudrnovsky <hellik@web.de> [2019-01-13 09:51:25 -0700]:

...

Is it the shebang line? I.e., it should be

`#!/usr/bin/env python`

instead of

`#!/usr/bin/python` ?

Bingo.

ag 'usr/bin/python'
r.estimap.recreation/test.r.estimap.recreation.py
1:#!/usr/bin/python\<nl>\

r.estimap.recreation/r.estimap.recreation.py
1:#!/usr/bin/python

All the other Python scripts use

#!/usr/bin/env python

So that needs to be fixed in your two scripts.

I've updated both. Hope to see it working tomorrow.

Great, the log is green! It installs and does not complain.

However, there is still a problem. I am under a Windows machine and have
installed GRASS 7.4.4, revision 70829 along with QGIS 2.18.27 (Nightly)
via the OSGeo4W installer.

I cannot launch the add-on. The path it is installed to is different
than the path GRASS is looking for it. The error message is an "Errno
2". No further hints.

While installing the add-on, or any other add-on for the matter, through QGIS,
via the GRASS plugin and the there-in GRASS Shell, I get two warnings:

- one is that GRASS_ADDON_BASE is not defined, thus the add-ons are
  installed under ~/.grass7/addons (I did confirm this)

- another, after the successful installation, is "WARNING: This add-on
  module will not function until you set the GRASS_ADDON_BASE
  environment variable (see "g.manual variables")

This is, in my view, difficult and eventually a blocker for
users without much of experience on all this.

Is this only my own "problematic" setup? Or is it like that for everyone
that will try to use OSGeo4W to install QGIS (Nightly) and GRASS and
then fetch those add-ons?

Nikos

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-14 10:14:48 +0100]:

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-13 23:31:26 +0100]:

* Markus Neteler <neteler@osgeo.org> [2019-01-13 19:43:10 +0100]:

On Sun, Jan 13, 2019 at 7:41 PM Nikos Alexandris
<nik@nikosalexandris.net> wrote:

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-13 19:26:04 +0100]:

* Helmut Kudrnovsky <hellik@web.de> [2019-01-13 09:51:25 -0700]:

...

Is it the shebang line? I.e., it should be

`#!/usr/bin/env python`

instead of

`#!/usr/bin/python` ?

Bingo.

ag 'usr/bin/python'
r.estimap.recreation/test.r.estimap.recreation.py
1:#!/usr/bin/python\<nl>\

r.estimap.recreation/r.estimap.recreation.py
1:#!/usr/bin/python

All the other Python scripts use

#!/usr/bin/env python

So that needs to be fixed in your two scripts.

I've updated both. Hope to see it working tomorrow.

Great, the log is green! It installs and does not complain.

However, there is still a problem. I am under a Windows machine and have
installed GRASS 7.4.4, revision 70829 along with QGIS 2.18.27 (Nightly)
via the OSGeo4W installer.

I cannot launch the add-on. The path it is installed to is different
than the path GRASS is looking for it. The error message is an "Errno
2". No further hints.

While installing the add-on, or any other add-on for the matter, through QGIS,
via the GRASS plugin and the there-in GRASS Shell, I get two warnings:

- one is that GRASS_ADDON_BASE is not defined, thus the add-ons are
installed under ~/.grass7/addons (I did confirm this)

- another, after the successful installation, is "WARNING: This add-on
module will not function until you set the GRASS_ADDON_BASE
environment variable (see "g.manual variables")

This is, in my view, difficult and eventually a blocker for
users without much of experience on all this.

Is this only my own "problematic" setup? Or is it like that for everyone
that will try to use OSGeo4W to install QGIS (Nightly) and GRASS and
then fetch those add-ons?

I see it is explained in the manual of `g.extension`, i.e.:

"The place where the extensions are installed can be customized by the
option prefix. Ensuring that these extensions will be accessible in
GRASS GIS is in this case in the responsibility of the user."

Should we add in this manual an example or two on how to set
GRASS_ADDON_BASE and a "typical" use case under windows?

Nikos

Hei Nikos,

Unfortunately, also under Windows people cannot necessarily choose where to install an addon, so that it ends up in HOME by default should be fine, and it should not be required to install addons in the man program directory system wide...

On Win10 with GRASS 7.4.0 from OSGeo4W I can install and run (open the GUI) of r.estimap.recreation without issue, though, when I run the module from CMD it opens both GUI and the python script in a text editor...

Cheers
Stefan

-----Original Message-----
From: grass-dev <grass-dev-bounces@lists.osgeo.org> On Behalf Of Nikos Alexandris
Sent: mandag 14. januar 2019 10:23
To: Markus Neteler <neteler@osgeo.org>
Cc: GRASS developers list <grass-dev@lists.osgeo.org>; Helmut Kudrnovsky <hellik@web.de>
Subject: Re: [GRASS-dev] Unable to install manual for add-on r.estimap.recreation under Windows

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-14 10:14:48 +0100]:

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-13 23:31:26 +0100]:

* Markus Neteler <neteler@osgeo.org> [2019-01-13 19:43:10 +0100]:

On Sun, Jan 13, 2019 at 7:41 PM Nikos Alexandris
<nik@nikosalexandris.net> wrote:

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-13 19:26:04 +0100]:

* Helmut Kudrnovsky <hellik@web.de> [2019-01-13 09:51:25 -0700]:

...

Is it the shebang line? I.e., it should be

`#!/usr/bin/env python`

instead of

`#!/usr/bin/python` ?

Bingo.

ag 'usr/bin/python'
r.estimap.recreation/test.r.estimap.recreation.py
1:#!/usr/bin/python\<nl>\

r.estimap.recreation/r.estimap.recreation.py
1:#!/usr/bin/python

All the other Python scripts use

#!/usr/bin/env python

So that needs to be fixed in your two scripts.

I've updated both. Hope to see it working tomorrow.

Great, the log is green! It installs and does not complain.

However, there is still a problem. I am under a Windows machine and
have installed GRASS 7.4.4, revision 70829 along with QGIS 2.18.27
(Nightly) via the OSGeo4W installer.

I cannot launch the add-on. The path it is installed to is different
than the path GRASS is looking for it. The error message is an "Errno
2". No further hints.

While installing the add-on, or any other add-on for the matter,
through QGIS, via the GRASS plugin and the there-in GRASS Shell, I get two warnings:

- one is that GRASS_ADDON_BASE is not defined, thus the add-ons are
installed under ~/.grass7/addons (I did confirm this)

- another, after the successful installation, is "WARNING: This add-on
module will not function until you set the GRASS_ADDON_BASE
environment variable (see "g.manual variables")

This is, in my view, difficult and eventually a blocker for users
without much of experience on all this.

Is this only my own "problematic" setup? Or is it like that for
everyone that will try to use OSGeo4W to install QGIS (Nightly) and
GRASS and then fetch those add-ons?

I see it is explained in the manual of `g.extension`, i.e.:

"The place where the extensions are installed can be customized by the option prefix. Ensuring that these extensions will be accessible in GRASS GIS is in this case in the responsibility of the user."

Should we add in this manual an example or two on how to set GRASS_ADDON_BASE and a "typical" use case under windows?

Nikos
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

* Stefan Blumentrath <Stefan.Blumentrath@nina.no> [2019-01-14 10:03:45
* +0000]:

Hei Nikos,

Unfortunately, also under Windows people cannot necessarily choose
where to install an addon, so that it ends up in HOME by default should
be fine, and it should not be required to install addons in the man
program directory system wide...

On Win10 with GRASS 7.4.0 from OSGeo4W I can install and run (open the
GUI) of r.estimap.recreation without issue, though, when I run the
module from CMD it opens both GUI and the python script in a text
editor...

Indeed. I was, without thinking too much, opting for system wide
installation. I removed all and re-installed the add-on without
checking the option to install it system-wide. It works!

I'll post in a new clean message, in this thread my next to-fix things.

Thank you Stefan

ps- Below relared text from previous message:

Nikos:

However, there is still a problem. I am under a Windows machine and
have installed GRASS 7.4.4, revision 70829 along with QGIS 2.18.27
(Nightly) via the OSGeo4W installer.

I cannot launch the add-on. The path it is installed to is different
than the path GRASS is looking for it. The error message is an "Errno
2". No further hints.

[..]

Is this only my own "problematic" setup? Or is it like that for
everyone that will try to use OSGeo4W to install QGIS (Nightly) and
GRASS and then fetch those add-ons?

I see it is explained in the manual of `g.extension`, i.e.: "The place
where the extensions are installed can be customized by the option
prefix. Ensuring that these extensions will be accessible in GRASS GIS
is in this case in the responsibility of the user."

Should we add in this manual an example or two on how to set
GRASS_ADDON_BASE and a "typical" use case under windows?

On Win10 with GRASS 7.4.0 from OSGeo4W I can install and run (open the GUI)

of r.estimap.recreation

without issue, though, when I run the module from CMD it opens both GUI and

the python script in a text >editor...

I can't reproduce it here.

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

Yeah, that can be an odd setting on my machine or related to my Notepad++ related settings... Not of importance.

But maybe Windows 10 again knows better than me what I want to do...

Or it is Microsofts new "Open Source Initiative", opening the source code of every tool one runs and presenting it to the user for inspection (I should probably try to start Word from CMD...).

Just kidding of course...

-----Original Message-----
From: grass-dev <grass-dev-bounces@lists.osgeo.org> On Behalf Of Helmut Kudrnovsky
Sent: mandag 14. januar 2019 13:30
To: grass-dev@lists.osgeo.org
Subject: Re: [GRASS-dev] Unable to install manual for add-on r.estimap.recreation under Windows

On Win10 with GRASS 7.4.0 from OSGeo4W I can install and run (open the GUI)

of r.estimap.recreation

without issue, though, when I run the module from CMD it opens both GUI and

the python script in a text >editor...

I can't reproduce it here.

-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

* Helmut Kudrnovsky <hellik@web.de> [2019-01-14 05:29:38 -0700]:

On Win10 with GRASS 7.4.0 from OSGeo4W I can install and run (open the GUI)

of r.estimap.recreation

without issue, though, when I run the module from CMD it opens both GUI and

the python script in a text >editor...

I can't reproduce it here.

Me neither actually.

Nikos

A few more hooks:

1. Having the add-on installed via a GRASS GIS session, using
`g.extension` (not from within QGIS), expectedly it would be available
from within the "GRASS Shell" under QGIS' GRASS plugin. However, trying
to launch the script from this "GRASS Shell" won't work? Different
environment variable settings I guess.

2. Performing the installation in QGIS' GRASS Shell, ends up with the
warnings about the GRASS_ADDON_BASE variable, the ones I mentioned
earlier in this thread.

What is a/the recommended way to proceed on this?

A request for comments:

Weeks ago, I received from Médéric Ribreux detailed instructions on how
to build an entry for a GRASS GIS add-on in QGIS' Processing toolbox. I
will load these somewhere in the Wiki or in trac. Nevertheless, I
decided to go the "GRASS plugin" way, rather than the "Processing"
toolbox. The reason is that creating the interface for Processing is a
lot of work as the add-on itself is quite big. Important updates in the
script itself would require to re-work on its interface for QGIS'
Processing. Using the "GRASS plugin" is way easier as it only requires
to update the QGIS-GRASS module configuration file (in other words: the
file named after the add-on's name with the extension .qgm).

My concern is how to achieve/ensure the add-ons inclusion under the
GRASS plugin? I recall Stefan's advise on this that I would need to
write a routine to perform the proper file-copy actions.

Would you please share your thoughts on this?

To-do:

- some left-over work related with the '@MapsetName' part of map names
  when using the GUI. I remember that `r.mapcalc` does not like this
  and it is required to do some "manual" work in the script to take care
  of it.

- update the manual.

- complete the QGIS-GRASS module configuration file

Thank you, Nikos

A first swift answer:
Currently, making an addon available in QGIS is quite similar comparing the options GRASS plugin and processing. In both cases you will have to redefine the GUI in either txt or xml.

That has been a design choice in QGIS (as modules were supposed to be simplified in QGIS).

That was one thing that Radek was trying to address when he started the GSoC project to overhaul GRASS integration in Processing for QGIS 3 (if I remember correctly). But this is unfinished work I am afraid...

Cheers
Stefan

-----Original Message-----
From: Nikos Alexandris <nik@nikosalexandris.net>
Sent: mandag 14. januar 2019 14:44
To: Stefan Blumentrath <Stefan.Blumentrath@nina.no>
Cc: GRASS developers list <grass-dev@lists.osgeo.org>; Helmut Kudrnovsky <hellik@web.de>
Subject: Re: [GRASS-dev] Unable to install manual for add-on r.estimap.recreation under Windows

A few more hooks:

1. Having the add-on installed via a GRASS GIS session, using `g.extension` (not from within QGIS), expectedly it would be available from within the "GRASS Shell" under QGIS' GRASS plugin. However, trying to launch the script from this "GRASS Shell" won't work? Different environment variable settings I guess.

2. Performing the installation in QGIS' GRASS Shell, ends up with the warnings about the GRASS_ADDON_BASE variable, the ones I mentioned earlier in this thread.

What is a/the recommended way to proceed on this?

A request for comments:

Weeks ago, I received from Médéric Ribreux detailed instructions on how to build an entry for a GRASS GIS add-on in QGIS' Processing toolbox. I will load these somewhere in the Wiki or in trac. Nevertheless, I decided to go the "GRASS plugin" way, rather than the "Processing"
toolbox. The reason is that creating the interface for Processing is a lot of work as the add-on itself is quite big. Important updates in the script itself would require to re-work on its interface for QGIS'
Processing. Using the "GRASS plugin" is way easier as it only requires to update the QGIS-GRASS module configuration file (in other words: the file named after the add-on's name with the extension .qgm).

My concern is how to achieve/ensure the add-ons inclusion under the GRASS plugin? I recall Stefan's advise on this that I would need to write a routine to perform the proper file-copy actions.

Would you please share your thoughts on this?

To-do:

- some left-over work related with the '@MapsetName' part of map names
  when using the GUI. I remember that `r.mapcalc` does not like this
  and it is required to do some "manual" work in the script to take care
  of it.

- update the manual.

- complete the QGIS-GRASS module configuration file

Thank you, Nikos

* Stefan Blumentrath <Stefan.Blumentrath@nina.no> [2019-01-14 14:03:29 +0000]:

A first swift answer: Currently, making an addon available in QGIS is
quite similar comparing the options GRASS plugin and processing. In
both cases you will have to redefine the GUI in either txt or xml.

Stefan, I don't think it's the same in terms of effor. I'll post the
instructions for 'Processing' and I think you will see the amount of
work you need to put there-in to add additional logic to the existing
(Python) methods.

Nikos

That has been a design choice in QGIS (as modules were supposed to be
simplified in QGIS).

That was one thing that Radek was trying to address when he started the
GSoC project to overhaul GRASS integration in Processing for QGIS 3 (if
I remember correctly). But this is unfinished work I am afraid...

Cheers Stefan

[rest deleted]

* Stefan Blumentrath <Stefan.Blumentrath@nina.no> [2019-01-14 13:01:49 +0000]:

Yeah, that can be an odd setting on my machine or related to my Notepad++ related settings... Not of importance.

But maybe Windows 10 again knows better than me what I want to do...

Or it is Microsofts new "Open Source Initiative", opening the source code of every tool one runs and presenting it to the user for inspection (I should probably try to start Word from CMD...).

Just kidding of course...

:smiley:

* Nikos Alexandris <nik@nikosalexandris.net> [2019-01-14 15:29:34 +0100]:

* Stefan Blumentrath <Stefan.Blumentrath@nina.no> [2019-01-14 14:03:29 +0000]:

A first swift answer: Currently, making an addon available in QGIS is
quite similar comparing the options GRASS plugin and processing. In
both cases you will have to redefine the GUI in either txt or xml.

Stefan, I don't think it's the same in terms of effor. I'll post the
instructions for 'Processing' and I think you will see the amount of
work you need to put there-in to add additional logic to the existing
(Python) methods.

Here a first draft: https://trac.osgeo.org/grass/wiki/QGIS-Processing-GRASS-Provider

I tool the liberty to retouch the text I received from Médéric Ribreux
(in Cc).

Nikos