where should the .o files end up?

Tue Jul 18 13:10:00 GMT 2000

> Does gcj re-compile .java files that are newer than corresponding
> .class files, even if not listed on the command line, in the same way
> that javac does?
>> Actually, I don't think gcj necessarily should, at least not by default
> and when compiling to .o files, as that may conflict too much with
> Makefile expectations. However, there should at least be an option to
> mimic javac behavior, and it should be the default when mimicing javac.

Another useful feature would be for gcj to do all the linking.
I.e. doing "gcj foo/bar/baz.java --main=foo.bar.baz" would recompile
all needed files, and then link them into an executable.
This would mean minimal makefiles for java projects, and be more like javac.
I'll poke around in the gcc driver, but I wouldn't bet on me actually
accomplishing anything.