[GRASS-user] Installing Addon without source tree?

[Markus Neteler]

On Thu, Oct 1, 2009 at 6:21 PM, Horacio Samaniego
<horacio.samaniego at gmail.com> wrote:
> this might be a question for more advanced users or even developers.

(yes)

> Is there a way to clarify what the equivalent of the grass_src would be
> if you´ve just installed the grass-dev?

There is a new script "g.extension" which should do the job:

- For 6.4, it is in addons (yes, IMHO that does't make much sense).
- For 6.5, it is part of the main software, and a shell script.
- For 7.svn, it is part of the main software, and a python script.

> A user would run into this issue if attempting to install an addon.
>
> For example, the great module developed by Jarek Jasiewicz
> (http://heretic.livenet.pl/heretic/)
>
> Off course, in my ignorance, I could try to go ahead and
> create /usr/lib/grass64/raster , place a directory with the contents of
> the addon in it and run make, bu I still get errors on compilation.

I think that you get an error which is different from the absence
of that directory.
It might be related to
http://trac.osgeo.org/grass/ticket/620

> The question is then, how should we setup the MODULE_TOPDIR variable
> from within the Makefile, if we do not want to install the whole
> grass_src tree? I have chosen to just keep the grass-dev package
> provided by my distro (ubuntu 9.04) as suggested in the wiki
> (http://grass.osgeo.org/wiki/Compile_and_Install#Addons).

You could try to set it as path to the binary tree but I am
not sure if that works (on Ubuntu).

> any extra hint for beginners like me? any help will be added to the wiki
> once it's solved.

Excellent. I would really like to see the installation of Addons
functional and g.extension be part of 6.4.0.

Markus