where should the .o files end up?

Tue Jul 18 12:10:00 GMT 2000

Mo> I am ok with using "gcj -c -o build/foo.o foo.java" for one file,
Mo> but what if you want to compile more than one .java file? With
Mo> javac, you can run "javac -d build *.java", it is really handy.
That's what Anthony was suggesting too.
I wouldn't mind this if there were an additional argument to gcj to
enable this feature. In fact I can imagine that it would be handy.
However, my reading is that this will require hacking gcc/gcc.c, since
file naming issues are handled by gcc itself. This makes it harder to
do; gcc.c is very ugly.
Could you submit a PR for this? It probably won't be implemented
anytime soon, unless someone volunteers.
Tom