[GRASS5] Re: Windows grass binaries / GRASS branching

[Bernhard Reiter]

On Mon, May 29, 2000 at 04:01:13PM +0700, Justin Hickey wrote:
> 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.
> > 
> > Especially 2. would be of general interest, I think.
> > If 1. is there, we could modularize the GRASS in a first approach
> > into smaller, topic-oriented packages. 
> > 
> > In fact the best solution would be that the compile script collects 
> > the *existing modules* first, then we would get rid of the
> > src/CMD/lists/GRASS.
> 
> I am not confident in shell programming, but I can easily write a perl
> script that can detrmine all exisiting modules if there is a way to
> determine if a directory is a module. 

If perl is not a prerequisitive for building GRASS now, we should not
introduce it.
	Bernhard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 236 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20000529/77b12561/attachment.bin