Re: where should the .o files end up?

[Jeff Sturm <jeff dot sturm at appnet dot com>]

Tom Tromey wrote:
> 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.

Yep.  Besides, to emulate what javac (or gcj -C) does, you must extract
the package name somehow from the source or bytecode, so gcc.c would
need a hook into the frontend.  Ick.

--
Jeff Sturm
jeff.sturm@appnet.com