On Friday 23 December 2005 06:34, Tom Tromey wrote: > I've checked in the Eclipse jar builder to Classpath head, and now my > fakejdk project is available. This means you can easily start > playing with an in-workspace VM in Eclipse. > > To do this, follow the wiki instructions to check out and build > Classpath and Cacao (as always, this VM is chosen because all the > needed build bits are in its cvs repository... hint to the other VM > developers). > > Once that is done, check out the fakejdk project from > > :pserver:[EMAIL PROTECTED]:/cvs/rhug, module 'fakejdk'. > > (This ought to auto-build, but if not, apply the usual Clean hack.) > This just makes a little project consisting of symlinks -- it is a > huge hack. > > Now, go to Window->Preferences->Java->Installed JREs and choose > 'Add...' to add a new one. I named mine "Cacao". For the JRE home > directory, choose $workspace/fakejdk. Then turn off "Use default > system libraries" and you can edit the Source attachment of the new > JRE to point to the classpath directory in the workspace.
when i do that Eclipse claims that "Target is not a JDK root. System library was not found." this turns out to be caused by the fact that the instructions to follow do not cause a glibj.zip to be generated, and hence be used as the fake rt.jar. > Once this is done you can pick this JRE for launchers, or to build > other projects against. This is nice because it means these projects > don't have to necessarily depend on Classpath -- there is a layer of > indirection, so you can build and run them against the system VM if > you prefer to do that, without modifying the shared build setup. > > Tom cheers; rsn
pgp0qXtfQwHMf.pgp
Description: PGP signature
_______________________________________________ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
