Just curious how one should use makefiles in grass as a user.
The problem is the results are seen deep in the file tree, not in the
current directory, therefore one needs to add, say a touch(1):
allone:
g.region s=2610000 n=2611000 w=254500 e=255800
r.mapcalc $@=1
touch $@
unless one wants to dabble in grass's internal paths. Do all these
touch(1)es sound smart?
--
http://jidanni.org/ Taiwan(04)25854780
On Sat, Dec 07, 2002 at 12:04:11PM +0800, Dan Jacobson wrote:
Just curious how one should use makefiles in grass as a user.
The problem is the results are seen deep in the file tree, not in the
current directory, therefore one needs to add, say a touch(1):allone:
g.region s=2610000 n=2611000 w=254500 e=255800
r.mapcalc $@=1
touch $@unless one wants to dabble in grass's internal paths. Do all these
touch(1)es sound smart?
Why is it you want to use makefiles for such things? Shell scripts are
probably a better option.
--
"...the plural of anecdote is [not?] data." - attrib. to George Stigler
"E" == Eric G Miller <egm2@jps.net> writes:
E> Why is it you want to use makefiles for such things? Shell scripts are
E> probably a better option.
Just like one would use makefiles in non-grass situations: to only do
the needed parts of a job. If X depends on Y and Z depends on Y, then
after I build Z, Y doesn't need to be rebuilt when I build X, etc.
I don't see how grass projects are special that makefiles wouldn't be
helpful (if it weren't for the fact that the products aren't in the
same directory.)
--
http://jidanni.org/ Taiwan(04)25854780