Hy list,
I’m working with some grass addons and I’d like to try this in OSGeoW but Is’nt not clear for me how can I do for compile and install single module. Are there tutorial? Could anybody help me?
thanks
ss
On Sun, Feb 15, 2009 at 12:10 AM, sirius spelta <sirius.spelta@gmail.com> wrote:
Hy list,
I'm working with some grass addons and I'd like to try this in OSGeoW but
Is'nt not clear for me how can I do for compile and install single module.
Are there tutorial? Could anybody help me?
In the main directory of the Addons is a README explaiing it:
http://trac.osgeo.org/grass/browser/grass-addons/README
OSGeoW specific questions are better posted to their
mailing list:
http://trac.osgeo.org/osgeo4w/
since the packagers are reading there.
Please report back if you solve it so that we can set up a
small tutorial in the OSGeoW trac Wiki.
Markus
On Sun, 15 Feb 2009 07:56:19 +0100,
Markus Neteler <neteler@osgeo.org> wrote:
On Sun, Feb 15, 2009 at 12:10 AM, sirius spelta <sirius.spelta@gmail.com> wrote:
Hy list, I'm working with some grass addons and I'd like to try this
in OSGeoW but Is'nt not clear for me how can I do for compile and
install single module. Are there tutorial? Could anybody help me?
In the main directory of the Addons is a README explaiing it:
http://trac.osgeo.org/grass/browser/grass-addons/README
OSGeoW specific questions are better posted to their mailing list:
http://trac.osgeo.org/osgeo4w/ since the packagers are reading there.
Please report back if you solve it so that we can set up a small
tutorial in the OSGeoW trac Wiki.
Trying to compile a module (v.in.gshhs) following these instructions I
did (first relevant output lines only):
---<--------------------cut here---------------start------------------->---
$ sudo make MODULE_TOPDIR=/usr/lib/grass64
mkdir -p /build/buildd/grass-6.4.0~rc4/bin.x86_64-pc-linux-gnu
mkdir -p /build/buildd/grass-6.4.0~rc4/dist.x86_64-pc-linux-gnu/include/grass
mkdir -p /build/buildd/grass-6.4.0~rc4/dist.x86_64-pc-linux-gnu/lib
mkdir -p /build/buildd/grass-6.4.0~rc4/dist.x86_64-pc-linux-gnu/bin
mkdir -p /build/buildd/grass-6.4.0~rc4/dist.x86_64-pc-linux-gnu/etc
mkdir -p /build/buildd/grass-6.4.0~rc4/dist.x86_64-pc-linux-gnu/driver
mkdir -p /build/buildd/grass-6.4.0~rc4/dist.x86_64-pc-linux-gnu/driver/db
mkdir -p /build/buildd/grass-6.4.0~rc4/dist.x86_64-pc-linux-gnu/fonts
test -d OBJ.x86_64-pc-linux-gnu || mkdir -p OBJ.x86_64-pc-linux-gnu
gcc -I/build/buildd/grass-6.4.0~rc4/dist.x86_64-pc-linux-gnu/include -Wall -g -O -I/usr/include/gdal -DPACKAGE=\""grassmods"\" -I/usr/include/gdal -I/build/buildd/grass-6.4.0~rc4/dist.x86_64-pc-linux-gnu/include -o OBJ.x86_64-pc-linux-gnu/main.o -c main.c
main.c:30:23: error: grass/gis.h: No such file or directory
main.c:31:24: error: grass/dbmi.h: No such file or directory
main.c:32:24: error: grass/Vect.h: No such file or directory
main.c:33:29: error: grass/gprojects.h: No such file or directory
main.c:34:27: error: grass/glocale.h: No such file or directory
---<--------------------cut here---------------end--------------------->---
This is in Debian sid AMD64 (with grass-dev installeds, I don't
understand why gis.h is not found), where the /build path doesn't exist.
What variable needs to be passed to 'make' to set that /build path so as
not to create such top level directories beyond GRASS that might pollute
the system? Thanks.
--
Seb