This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: example of using ant to drive a gcj build
Andrew Pimlott <andrew@pimlott.net> writes:
> Shell is still the natural choice for writing most rules, don't you
> agree (not that it wouldn't be nice to have a choice)?
My big beef is 'find'. Actually, this is one case where XML might
actually help. A lot of the complex search queries I use are
tree-structured ((A OR B) AND (C OR D)), which lends itself more to
XML (or S-exps, or whatever) than a list of arguments on the command
line.
> Here you want a real programming language.
Has anybody produced a make with a builtin 'find'-ish feature? It
seems like it would be nice to integrate the dependancy tool with the
file-set-specification tool.
> As long as you don't have filenames with spaces in them (in which
> case, make is useless), it doesn't tend to bite.
Hrm, I'm not too good with the shell, but if you put find in backticks
and some of the files have shell metacharacters in their names, won't
this confuse the "outer" invocation of the shell?
- a