[GRASS-user] AddOn or Script when compiling GRASS from source

Glynn Clements glynn at gclements.plus.com
Sun Oct 23 09:39:23 EDT 2011

Martin Landa wrote:

> >> If GRASS_ADDON_PATH is just for executables, how are libraries, manual
> >> pages, etc, supposed to be found?
> >
> > It requires other variables like GRASS_ADDON_ETC, GRASS_ADDON_LIB, it
> > was a main reason why I changed it in G7. AFAIU Hamish would like to
> > define in G7 two variables, GRASS_ADDON_BASE (g.extension) and
> > GRASS_ADDON_PATH eg. for user scripts (?)
> so what's the preferred solution for G7
> 1) single variable GRASS_ADDON_PATH for all components (as it is)
> 2) two variables - GRASS_ADDON_BASE and GRASS_ADDON_PATH (path only as in G6)

#1. Although the name doesn't matter.

If the user wants to add extra executable directories, they can modify
PATH directly.

Glynn Clements <glynn at gclements.plus.com>

More information about the grass-user mailing list