Re: groan: installation

[Adam Megacz <gcj at lists dot megacz dot com>]

Momchil Velikov <velco@fadata.bg> writes:
> Yes, and potential imprecise (overly conservative) tracking of
> dependencies. How can ANT help with this [1]?

There are many answers, but here are two off the top of my head:

1. Ant <fileset/>s are more flexible and easier to read than
   backtick-wrapped invocations of 'find'.  You also don't run into
   problems with limitations on command line length.

2. Ant's <apply/> task is ideally suited to mapping an operation onto
   a directory tree in order to produce a second directory tree.  For
   example, running gcjh on a huge directory tree full of .class
   files, and generating an equivalently-structured tree of .h files.
   Apply can also do up-to-dateness checks.

I don't know... I just think it's ridiculous that libgcj/Makefile.am
has a list of every single .java file, and that list has to be kept up
to date by hand.  To me, that screams "your build tool is not doing
its job".

  - a


-- 
"Through your rags I see your vanity"  -- Socrates