fyi I get what it does now, and just fixed a small bug in it which was stopping it from reading CELL maps.
I have the full svn version of grass built from source, and from the addons svn dir I built it with: make MODULE_TOPDIR=/usr/local/src/grass/svn/grass65/ (I just run grass out of the source dir, so never 'make install' it) at minimum I think you have to cd to the main source dir and do ./configure if you installed grass from a package, check if there is an associated -dev package, and then point MODULE_TOPDIR towards where it install its files. Hamish LeeDaniel wrote: > Thanks for the replies! I've tried it out and here are my > responses to the > suggestions: > > @ Markus - Downloaded the script and put it in my scripts > folder, made it > executable and made it assigned rights to myself. Just as a > test I tried > opening it as a GUI and, lo and behold, it worked. However, > it couldn't find > my add-on path, of course, when I tried to add r.area. So I > went to the > terminal and entered: > > export GRASS_ADDON_PATH?$GISBASE > g.extension r.area > > Now things looked good. It did the following: > > Fetching <r.area> from GRASS-Addons SVN (be > patient)... > A r.area/main.c > A r.area/description.html > A r.area/Makefile > Checked out revision 42910. > - Great, got the files needed. Then it started compiling: > Compiling <r.area>... > mkdir -p > /usr/src/packages/BUILD/grass-6.4.0RC6/bin.i686-pc-linux-gnu > mkdir -p > /usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/include/grass > mkdir -p > /usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/lib > mkdir -p > /usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/bin > mkdir -p > /usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/etc > mkdir -p > /usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/driver > mkdir -p > /usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/driver/db > mkdir -p > /usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/fonts > test -d OBJ.i686-pc-linux-gnu || mkdir -p > OBJ.i686-pc-linux-gnu > gcc > -I/usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/include > > -O2 > -DPACKAGE=\""grassmods"\" > -I/usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/include > -o > OBJ.i686-pc-linux-gnu/main.o -c main.c > main.c:19:23: fatal error: grass/gis.h: No such file or > directory > compilation terminated. > make: *** [OBJ.i686-pc-linux-gnu/main.o] Error 1 > ERROR: Compilation failed, sorry. Please check above error > messages. > - So it looks like it was able to make a bunch of > directories. I checked, > they're there, new as of today. The entire directory of > /usr/src/packages/ > is new. However, GRASS wasn't able to compile. I checked > for > > /usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/include/grass/gis.h > since it seemed that it was looking for it and couldn't > find it, and > discovered that the directory > /usr/src/packages/BUILD/grass-6.4.0RC6/dist.i686-pc-linux-gnu/include/grass/ > is completely empty. Could that be the problem? I also > tried using > sudo g.extension r.area > And got the usual error that I have to be in GRASS GIS to > run the program. I > didn't try starting GRASS as a super user because I don't > want to do > anything wrong and I also don't want it to install r.area > only for super > users. > > But that would be a nice way of loading add-ons, because it > looks like I > wouldn't have to have the source code all on my hard drive. > Any idea why > it's not working? > > @ Micha - Tried running it with g.extension (see above); it > didn't work, so > I tried to do the thing manually again. Entered > svn checkout https://svn.osgeo.org/grass/grass-addons/ > grass-addons > to get the source codes. It worked and all the source codes > were downloaded > to my home directory in the folder grass-addons. Then I > navigated into the > directory > ~/grass-addons/raster/r.area/ > and entered the command > ./configure > This is similar to last time; last time, I also had been > inside the > directory when I tried the commands. But I thought hey, > maybe I'd copied the > source codes wrong. Sadly, that doesn't seem to be the > problem; just like > last time, I got the message > bash: ./configure: No such file or directory > I then tried it as super user. Same problem. > > Any other ideas? Thanks a lot again for the help, > everyone! > Daniel _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user