This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: .db -vs- resources
- From: Andrew Haley <aph at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: GCJ Hackers <java at gcc dot gnu dot org>
- Date: Thu, 17 Mar 2005 10:04:50 +0000
- Subject: Re: .db -vs- resources
- References: <m3mzt3dseq.fsf@localhost.localdomain>
Tom Tromey writes:
> Something that came up on irc the other day is that if you're using
> the .db to find .sos, then a resource in the .so will actually never
> be used; instead the resource from the original .jar (or whatever)
> will be used.
Yeah, this is deliberate. Clearly we have a choice here, and to do
otherwise would require the checksum of the resource to be stored in
the .db file. We'd only generate the checksum and then look up the
same thing in a shared object!
> In this case, compiling a resource file in a .jar into the
> resulting .so is just bloat. It would be nice to have a gcj flag
> controlling this behavior.
Yes.
Andrew.