[GRASS-dev] file input for r.reclass etc

Hamish,

Perhaps I misunderstood, but I read a recent post of yours to suggest that ‘file=’ arguments had been added to r.reclass and r.recode. However, I just recompiled from a cvs update and I don’t see them. Did I miss something?

Michael


Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

Michael Barton wrote:

Perhaps I misunderstood, but I read a recent post of yours to suggest that
'file=' arguments had been added to r.reclass and r.recode. However, I just
recompiled from a cvs update and I don't see them. Did I miss something?

AFAICT, this was discussed but hasn't actually been added yet.

I'll look into it.

--
Glynn Clements <glynn@gclements.plus.com>

Glynn Clements wrote:

> Perhaps I misunderstood, but I read a recent post of yours to suggest that
> 'file=' arguments had been added to r.reclass and r.recode. However, I just
> recompiled from a cvs update and I don't see them. Did I miss something?

AFAICT, this was discussed but hasn't actually been added yet.

I'll look into it.

I've added a rules= option to r.reclass, although it hasn't been
tested yet.

--
Glynn Clements <glynn@gclements.plus.com>

Thanks, I'll try to recompile and take a look tonight.

Michael

On 6/25/07 4:16 PM, "Glynn Clements" <glynn@gclements.plus.com> wrote:

Glynn Clements wrote:

Perhaps I misunderstood, but I read a recent post of yours to suggest that
'file=' arguments had been added to r.reclass and r.recode. However, I just
recompiled from a cvs update and I don't see them. Did I miss something?

AFAICT, this was discussed but hasn't actually been added yet.

I'll look into it.

I've added a rules= option to r.reclass, although it hasn't been
tested yet.

__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

Glynn Clements wrote:

> > Perhaps I misunderstood, but I read a recent post of yours to suggest that
> > 'file=' arguments had been added to r.reclass and r.recode. However, I just
> > recompiled from a cvs update and I don't see them. Did I miss something?
>
> AFAICT, this was discussed but hasn't actually been added yet.
>
> I'll look into it.

I've added a rules= option to r.reclass, although it hasn't been
tested yet.

Also for r.recode.

--
Glynn Clements <glynn@gclements.plus.com>

Glynn,

I recompiled all of GRASS (after a make distclean) just before you committed
your change to r.recode. Then I just updated and compiled r.recode, without
recompiling all the rest. Is this a problem? Do I need to recompile the
whole enchilada again?

Michael

On 6/25/07 7:41 PM, "Glynn Clements" <glynn@gclements.plus.com> wrote:

Glynn Clements wrote:

Perhaps I misunderstood, but I read a recent post of yours to suggest that
'file=' arguments had been added to r.reclass and r.recode. However, I just
recompiled from a cvs update and I don't see them. Did I miss something?

AFAICT, this was discussed but hasn't actually been added yet.

I'll look into it.

I've added a rules= option to r.reclass, although it hasn't been
tested yet.

Also for r.recode.

__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

Michael Barton wrote:

I recompiled all of GRASS (after a make distclean) just before you committed
your change to r.recode. Then I just updated and compiled r.recode, without
recompiling all the rest. Is this a problem? Do I need to recompile the
whole enchilada again?

No.

You don't need to compile from scratch if the only files which have
changed are the source and header files in the module's directory. The
Makefile will notice that those have changed and re-compile what's
required (if any header file in the directory changes, it will
re-compile all object files).

You only need to force re-compilation (with "make clean") if there is
a change to a dependency which isn't listed as such in the module's
Makefile. This essentially means a change to the project-wide header
files, the Makefile fragments in include/Make, the configure script or
the libraries.

If a library is modified, you can just run "make" on the library's
directory, then on the directories of the modules which use it. The
modules will be re-linked if any of the libraries which they use have
changed. Running "make" from the top-level directory will handle all
of this (re-compiling libraries and re-linking whatever uses them),
without re-compiling or re-linking anything unnecessarily.

OTOH, If there are changes to project-wide header files or the
Makefile fragments, you really need to run "make clean" first, as
there is no record of whether a file depends upon any of these.
Similarly, if the configure script changes, you need to run "make
distclean" then re-run configure.

--
Glynn Clements <glynn@gclements.plus.com>