Sounds like Debian could use the same solution for gcj that Debian uses for emacs -> just distribute the .java files and do the ahead-of-time compilation (.java to .so) at install time. Is this automatic enough under gcj so that this could that work?
Granted, the emacs solution is currently a bit klunky for the users, who have to put up with long compiles during install, but it does take the load off of the maintainers to have to precompile their stuff for multiple targets. Cheers, - Jim On Sun, 2002-05-12 at 16:28, Stephen Zander wrote: > >>>>> "Andrew" == Andrew Pimlott <[EMAIL PROTECTED]> writes: > Andrew> To clarify, I'm talking about Java code compiled (eg, by > Andrew> gcj) into architecture-specific machine code. These > Andrew> libraries are still meant to be used by Java code (also > Andrew> compiled with gcj), not C code. So I think java should > Andrew> still be part of the name. > > That statement is true iff you can use the gjc produced .so files with > kaffa/jdk/etc without *any* additional coding/configuratiojn/whatever. > I don't think that condition is satisfiable right now. > > .java => gjc => executable/shared object is a one-way function. > > -- > Stephen > > "A duck!" > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
