[GRASS5] Re: Windows grass binaries / GRASS branching

Markus Neteler neteler at geog.uni-hannover.de
Mon May 29 13:59:44 EDT 2000

Hello again,

(sorry for so many mails)

On Mon, May 29, 2000 at 04:01:13PM +0700, Justin Hickey wrote:
> Hello Markus
> On Fri, 26 May 2000, Markus Neteler wrote:
> > The only problem is the
> > src/CMD/lists/GRASS which is parsed for compilation. Either
> > we have to hold two lists (stable/unstable) or the compile
> > mechanism needs to be modified to 
> > 
> >  1. ignore non-existing modules (as they might not have been checked
> >     out if the stable version was acquired)
> >  2. ignore compile errors and proceed, maybe collecting the
> >     names of uncompiled modules in a log file.

Both I could manage easily by modifying

Now "error.log" is created locally, containing such messages:

Compilation error at STEP: src/raster/r.cost (ignored)
Compilation error at STEP: src/raster/r.sss (ignored)

(Note: the r.cost error is a fake, no need to become nervous)

This means we can keep the full
list. The user could compile even if having only a sub-set of
modules (in case GRASS will be shipped in packages).

So: Shall I apply this patch?

Best wishes


If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'

More information about the grass-dev mailing list