Okay from how I understand it: The classloader is not altered and must still use Jars (since applications, like Eclipse, do override and make their own classloader). The classloader returns a byte[] representing the resource to the VM, which is responsible for actually running it. THe GCJ stuff takes teh byte[], hashes it, and looks up the native piece using the hash.
This means the original byte[] is required, the Jar is required. Correct me if I'm wrong. On Sat, 2005-04-30 at 19:51 +0200, Michael Koch wrote: > On Sat, Apr 30, 2005 at 01:15:04PM -0500, Jerry Haltom wrote: > > I mean as part of the arch-dep process. THe arch-dep process requires a > > complete build, simply excluding everything else from the package. > > > > Of course the jars are still required. They have things in them other > > than .class files. > > These things *CAN* be compiled as resources into the libraries. > > I dont know if this is done currently and how buggy it is. There were > some bugs with this in the past. > > > Michael -- Jerry Haltom <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
