On Wed, Oct 11, 2000 at 04:42:20PM +0700, Justin Hickey wrote:
Hi Markus
I just had a thought that we don't need the src/CMD/next_step/ directory
anymore. The grass make process continues if any errors are encountered
so it will always go through all modules. Thus the purpose of the
next_step directory (allowing compilation to continue where an error
occured) is now redundant. What do you think?
Hi Justin,
the *only* use is, when you interrupt the compilation process
and restart it again. But nowadays machines are quite fast, the
process could even be started from scratch and the compiler would
run through all stuff again (partly without compiling).
I agree to remove it. It is even a good idea to start the
"make install" always from beginning as new users don't know
that they have to delete the src/CMD/next_step/* file if they
want to recompile the entire thing.
Developers, any objections here?
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Wed, Oct 11, 2000 at 11:38:27AM +0100, Markus Neteler wrote:
On Wed, Oct 11, 2000 at 04:42:20PM +0700, Justin Hickey wrote:
> Hi Markus
>
> I just had a thought that we don't need the src/CMD/next_step/ directory
> anymore. The grass make process continues if any errors are encountered
> so it will always go through all modules. Thus the purpose of the
> next_step directory (allowing compilation to continue where an error
> occured) is now redundant. What do you think?
Hi Justin,
the *only* use is, when you interrupt the compilation process
and restart it again. But nowadays machines are quite fast, the
process could even be started from scratch and the compiler would
run through all stuff again (partly without compiling).
I agree to remove it. It is even a good idea to start the
"make install" always from beginning as new users don't know
that they have to delete the src/CMD/next_step/* file if they
want to recompile the entire thing.
Developers, any objections here?
We should add a description on how to compile a single module.
Sometimes I want debugging or experimental flags for just one module.
We should have instructions on how to do this.
Bernhard
--
Professional Service around Free Software (intevation.net)
The FreeGIS Project (freegis.org)
Association for a Free Informational Infrastructure (ffii.org)
On Wed, Oct 11, 2000 at 02:07:21PM +0200, Bernhard Reiter wrote:
On Wed, Oct 11, 2000 at 11:38:27AM +0100, Markus Neteler wrote:
> On Wed, Oct 11, 2000 at 04:42:20PM +0700, Justin Hickey wrote:
> > Hi Markus
> >
> > I just had a thought that we don't need the src/CMD/next_step/ directory
> > anymore. The grass make process continues if any errors are encountered
> > so it will always go through all modules. Thus the purpose of the
> > next_step directory (allowing compilation to continue where an error
> > occured) is now redundant. What do you think?
> Hi Justin,
>
> the *only* use is, when you interrupt the compilation process
> and restart it again. But nowadays machines are quite fast, the
> process could even be started from scratch and the compiler would
> run through all stuff again (partly without compiling).
>
> I agree to remove it. It is even a good idea to start the
> "make install" always from beginning as new users don't know
> that they have to delete the src/CMD/next_step/* file if they
> want to recompile the entire thing.
>
> Developers, any objections here?
We should add a description on how to compile a single module.
Done. I have added a short passage to
INSTALL
Sometimes I want debugging or experimental flags for just one module.
We should have instructions on how to do this.
To be done... volunteers?
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'