Wed Sep 13 18:27:00 GMT 2000
>>>>> "Jeff" == Jeff Sturm <email@example.com> writes:
Jeff> A related issue is the runtime classpath. Should programs
Jeff> compiled by gcj also search /usr/share/gcj at runtime, or should
Jeff> they use the same classpath as the compiler? Right now
Jeff> libgcj.zip doesn't appear in the java.class.path system
Jeff> property; we may have to fix that someday for class resources.
I think for compiled programs it makes the most sense to not have to
ship the .class files with the program. To me that means we should
have a way to compile a property file and put it into the executable.
This subject has come up here before but it hasn't really been
important enough for anybody to implement.
I picture being able to take an executable .jar and compile it to a
standalone executable with one command. That would be convenient.
Jeff> While you're making the change, you might consider renaming to
Jeff> libgcj.jar since .zip really ought to be deprecated.
This will happen when we merge libgcj into the gcc tree. We've
already promised RMS that we will not use zip (since it is non-free).
Unless something comes up we're planning to use fastjar. (This, btw,
is why AG did all the jar-related work he did in the last month or so
-- he's planning ahead.)
More information about the Java