Re: [GRASS-dev] Scripting programming: directory structure of GRASS

Hi, http://grass.osgeo.org/grass63/manuals/html63_user/variables.html#enviro GRASS_ADDON_PATH [grass startup script] allows to specify additional paths to local GRASS modules extra to standard distribution. so, if you set $GRASS_ADDON_PATH (e.g. in ~/.grass.bashrc) and put your program there

[GRASS-dev] Scripting programming: directory structure of GRASS

Hi, I'm writing a script for Grass. I've a problem with the directory structure of GRASS. I know where is the place of script: ($GISBASE/scripts). But my script use some fortran-codes, I compile this codes with gfortran, and I don't know where's the correct directory for the executable compiled.

Re: [GRASS-dev] WinGRASS needs TclTk 8.4

On Feb 1, 2008, at 5:09 AM, Glynn Clements wrote: #include "tkMacOSX.h" #include These are only needed when using the Aqua TclTk. X11 TclTk on OSX is pure unix (and the one I recommend). I would recommend getting the native version to build. It shouldn't be necessary to h

Re: [GRASS-dev] Autoconf 2.13

> Glynn Clements <[EMAIL PROTECTED]> writes: >>> ? GRASS doesn't use automake, so I'm not sure what you mean >>> here. I'm sure if we *were* using automake, we'd also be quite keen >>> to move away from it towards something simpler and better! IMHO the >>> GRASS build system is refreshing

[GRASS-dev] patch for v.voronoi/v.delaunay

Hi all, As per request, I have patched v.delaunay (source in v.voronoi/) very carefully. The memory handling now seems to work better. At least I was able to triangulate a map with ca 3 points. Anything more and my system starts thrashing badly (1 GB, with a lot of other apps running). Feel f

Re: [GRASS-dev] lib fn to convert int color number to RGB values?

> Glynn Clements <[EMAIL PROTECTED]> writes: [...] >>> The GRASS libraries are fundamentally designed to be used in >>> "one-shot" modules. Errors are handled by printing a message then >>> exiting. Variables are either initialised at startup from the .data >>> and .bss segments or are in

Re: [GRASS-dev] lib fn to convert int color number to RGB values?

> Glynn Clements <[EMAIL PROTECTED]> writes: >>> RGBA_Color was recently added (as was RGB support for modules' CLI >>> options) [...] >> Could the attached (untested) patch be of any help? > First, you would need: > -typedef struct > +typedef struct RGBA_Color > { > unsigned c

Re: [GRASS-dev] new digitization tool compilation

Jachym Cepicky wrote: > I try to compile new wx v.digit, however without success: > > make > [...] > c++ -c -c -fpic > -I/home/jachym/src/grass/grass_trunk/dist.i686-pc-linux-gnu/include > -I/usr/include/python2.5 `wx-config --cxxflags` > grass6_wxvdigit_wrap.cxx -o OBJ.i686-pc-linux-gnu/grass6_

Re: [GRASS-dev] lib fn to convert int color number to RGB values?

> Hamish <[EMAIL PROTECTED]> writes: [...] >> s/RGB_Color/RGBA_Color/ ? > no, the idea there was to be a shortcut for those who wanted to use > the struct but didn't care about alpha and didn't want to cause > confusion in the variable namespace. In those cases the alpha channel > is i

Re: [GRASS-dev] [GRASS GIS] #33: config.in: cairo and ffmpeg checks

Lars Ahlzen wrote: > > we should finish adding Cairo support by building it into the ./configure > > script. > > > > the attached patch also adds an extra test needed for ffmpeg. > > > > I do not know much about autoconf and ./configure scripts so I don't claim > > that the attached patch

Re: [GRASS-dev] lib fn to convert int color number to RGB values?

Ivan Shmakov wrote: > > RGBA_Color was recently added (as was RGB support for modules' CLI > > options) so 1) it could be used to pass RGB arround without having to > > call the display library and 2) we could handle a color value of > > 'none' without needing to pass a separate variable or r

Re: [GRASS-dev] lib fn to convert int color number to RGB values?

Ivan Shmakov wrote: > >>> The former is only an advantage if there's a situation where a > >>> module doesn't just call G_fatal_error() when an invalid colour > >>> occurs. Given that invalid user input is usually a fatal error, I > >>> can't immediately think of a situation where you might g

[GRASS-dev] Issue with gnome-terminal [Re: Fwd: [GRASS-user] Page 37 "Open Source GIS" by Neteler & Mitasova]

On 31/01/08 23:34, Matt wrote: From: *Matt* <[EMAIL PROTECTED] > Date: Jan 28, 2008 8:59 PM Subject: Re: [GRASS-user] Page 37 "Open Source GIS" by Neteler & Mitasova To: Markus Neteler <[EMAIL PROTECTED] > Thanks for the quick reply. When I

Re: [GRASS-dev] Autoconf 2.13

Ivan Shmakov wrote: > > ? GRASS doesn't use automake, so I'm not sure what you mean > > here. I'm sure if we *were* using automake, we'd also be quite keen > > to move away from it towards something simpler and better! IMHO the > > GRASS build system is refreshingly simple to understand comp

Re: [GRASS-dev] d.histogram: font issue

Michael Barton wrote: > >>> I support using some Python plotting library to draw axes. We could > >>> write > >>> up a grid template using d.graph, but I'd rather be in the > >>> business of > >>> gluing together high quality components rather than reinventing > >>> yet-another x-y plotting pac

Re: [GRASS-dev] WinGRASS needs TclTk 8.4

William Kyngesburye wrote: > On Jan 31, 2008, at 3:40 AM, Glynn Clements wrote: > > > It still needs some "internal" files on Windows and MacOSX, > > specifically: > > > > > MacOSX: > > These don't appear to be in the GRASS source any more. > > > > > #include > > This is an old Mac "Cla

Re: [GRASS-dev] convert 3D polygons or Tins to a DEM?

In sw_main.c, function readsite ( void ) I find this: sites = (struct Site *) myalloc(4000*sizeof(*sites)); Since the "sites" structure is meant to contain all points of the input map: why is it allocated to a pre-defined number of 4000? Should this not rather be the number of points in the input

[GRASS-dev] new digitization tool compilation

Hi, I try to compile new wx v.digit, however without success: make [...] c++ -c -c -fpic -I/home/jachym/src/grass/grass_trunk/dist.i686-pc-linux-gnu/include -I/usr/include/python2.5 `wx-config --cxxflags` grass6_wxvdigit_wrap.cxx -o OBJ.i686-pc-linux-gnu/grass6_wxvdigit_wrap.o In file included fr

[GRASS-dev] new digitization tool compilation

Hi, I try to compile new wx v.digit, however without success: make [...] c++ -c -c -fpic -I/home/jachym/src/grass/grass_trunk/dist.i686-pc-linux-gnu/include -I/usr/include/python2.5 `wx-config --cxxflags` grass6_wxvdigit_wrap.cxx -o OBJ.i686-pc-linux-gnu/grass6_wxvdigit_wrap.o In file included fr