hej,
Am 03.03.2011 um 07:01 schrieb Hamish:
William wrote:
g.extension also changes how GRASS_ADDON_PATH is
interpreted, from GRASS 6 - it used to be a direct path to
the executable folder, ie bin/, now it's a path to the
parent of that. The default user addon paths set by
the Mac startup are (GRASS version is major.minor version):
It still should be a single path which points to a dir which should be
added to GRASS's search $PATH.
yes, g.extension is abusing it a bit using it like --prefix, but some
months ago g.extension was reworked with a hack so a symlink to the
executable made it into the real $GRASS_ADDON_PATH and not some
support
dir beneath it.
it is far from ideal, but it should make it work.. at least when the
install is built from a local compile. not sure how well tested it is
outside of that (where Platform.make and friends need to point to the
installed dir not the build dir, which doesn't exist on the end-users'
computer)
Hamish
It seems that my g.extension points to the build dir
rather then to the installation. So what should I do to install a add-
on which is executable
(globally) on my mac.?
I tried it also with /Library/GRASS/[GRASS version]/Modules/bin but i
still fail to compile and it still points to my build dir...
is there any other good way to install an add on on a mac?
maybe you can explain in detail how to do that, i really don't have a
clue after the readme...
/j
_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user
_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user
