Re: Using a workspace-based VM in Eclipse
On Sun, 2006-01-08 at 19:11 +0100, Christian Thalinger wrote: > But not everyone is compiling CACAO in eclipse. We need a more common > solution. Searching for a java compiler seems to be the best approach, > but how should this be done? Ok, again i found a good macro on http://ac-archive.sourceforge.net/, namely AC_PROG_JAVA. CACAO is now using these two files: http://ac-archive.sourceforge.net/Java_Support/ac_prog_javac.html http://ac-archive.sourceforge.net/Java_Support/ac_prog_javac_works.html I removed guavac and added ecj. I hope this is working for most people. TWISTI ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
On Sun, 2006-01-08 at 10:29 -0700, Tom Tromey wrote: > Ideally we would somehow use Eclipse's built-in compiler, but this is > a pain since we've set Cacao up as a C project... Eclipse is kind of > limited here. Since we can't do that, second best is to search for > some other java compiler. But not everyone is compiling CACAO in eclipse. We need a more common solution. Searching for a java compiler seems to be the best approach, but how should this be done? TWISTI ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
> "Twisti" == Christian Thalinger <[EMAIL PROTECTED]> writes: Twisti> http://b2.complang.tuwien.ac.at/cgi-bin/bugzilla/show_bug.cgi?id=13 Twisti> I'll fix that ASAP. Should i grab the code from classpath? Personally I find Classpath's javac configury code to be pretty ugly. (But I've also never felt the need to fix it...) Ideally we would somehow use Eclipse's built-in compiler, but this is a pain since we've set Cacao up as a C project... Eclipse is kind of limited here. Since we can't do that, second best is to search for some other java compiler. Tom ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
On Fri, 2006-01-06 at 04:33 -0800, Anthony Green wrote: > This worked pretty well for me, thanks. I wasn't able to get cacao via > cvs (server down?), so I used jamvm. The only gotcha I had is that Yes, it was down (harddisk crash). It's up again and should work. TWISTI ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
On Fri, 2006-01-06 at 17:23 -0700, Tom Tromey wrote:
> Raif> doesn't cacao also use jikes? (ref.
> Raif> ${CACAO_HOME}/src/lib/vm/reference/Makefile.am)
>
> Yeah. Both VMs should be fixed :-)
Thomas Fitzsimmons already filled a bug:
http://b2.complang.tuwien.ac.at/cgi-bin/bugzilla/show_bug.cgi?id=13
I'll fix that ASAP. Should i grab the code from classpath?
TWISTI
___
Classpath mailing list
Classpath@gnu.org
http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
> "Raif" == Raif S Naffah <[EMAIL PROTECTED]> writes:
>> I just did 'yum install jikes'. We ought to fix this though.
Raif> doesn't cacao also use jikes? (ref.
Raif> ${CACAO_HOME}/src/lib/vm/reference/Makefile.am)
Yeah. Both VMs should be fixed :-)
Tom
___
Classpath mailing list
Classpath@gnu.org
http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
On Saturday 07 January 2006 01:55, Tom Tromey wrote:
> > "Anthony" == Anthony Green <[EMAIL PROTECTED]> writes:
>
> Anthony> This worked pretty well for me, thanks. I wasn't able to
> get Anthony> cacao via cvs (server down?), so I used jamvm. The only
> Anthony> gotcha I had is that jamvm requires jikes to build, which I
> Anthony> did't have installed. Manually changing the Makefile jikes
> Anthony> reference to ecj worked.
>
> I just did 'yum install jikes'. We ought to fix this though.
doesn't cacao also use jikes? (ref.
${CACAO_HOME}/src/lib/vm/reference/Makefile.am)
cheers;
rsn
pgpGhNIbTWPFq.pgp
Description: PGP signature
___
Classpath mailing list
Classpath@gnu.org
http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
> "Anthony" == Anthony Green <[EMAIL PROTECTED]> writes: Anthony> This worked pretty well for me, thanks. I wasn't able to get Anthony> cacao via cvs (server down?), so I used jamvm. The only Anthony> gotcha I had is that jamvm requires jikes to build, which I Anthony> did't have installed. Manually changing the Makefile jikes Anthony> reference to ecj worked. I just did 'yum install jikes'. We ought to fix this though. Tom ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
On Thu, 2005-12-22 at 12:34 -0700, 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. This worked pretty well for me, thanks. I wasn't able to get cacao via cvs (server down?), so I used jamvm. The only gotcha I had is that jamvm requires jikes to build, which I did't have installed. Manually changing the Makefile jikes reference to ecj worked. Running single mauve testlets in Eclipse is pretty sweet! AG ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
hello Mark, On Friday 23 December 2005 21:56, Mark Wielaard wrote: > On Fri, 2005-12-23 at 19:56 +1100, Raif S. Naffah wrote: > > > 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. > > Are you sure you have the latest GNU Classpath CVS checked out in > eclipse? Tom added a new Builder ClasspathJar that generates a > glibj.zip after everything else has been build. See classpath Project > -> Properties -> Builders. looks like i didn't when i tried it earlier. works like a charm. thanks + cheers; rsn pgpvyl84aVnt2.pgp Description: PGP signature ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
Hi Raif, On Fri, 2005-12-23 at 19:56 +1100, Raif S. Naffah wrote: > > 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. Are you sure you have the latest GNU Classpath CVS checked out in eclipse? Tom added a new Builder ClasspathJar that generates a glibj.zip after everything else has been build. See classpath Project -> Properties -> Builders. Cheers, Mark signature.asc Description: This is a digitally signed message part ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
Hi Robert, On Thu, 2005-12-22 at 23:40 +, Robert Lougher wrote: > On 22 Dec 2005 12:34:42 -0700, Tom Tromey <[EMAIL PROTECTED]> wrote: > > 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). > > > Hint taken. The necessary files are now in JamVM's cvs repository. > This is your patch with a couple of changes by Raif that adds the > .cvsignore files and adds an Autogen Builder to create, among other > things, the configure script. Wee! This is cool. I needed one small patch to make it all work smoothly with the fakejdk project. Besides building everything jamvm should also be installed and then you can just automagically switch fakejdk to use jamvm (it will automatically select jamvm if cacao isn't available). Now my eclipse based projects can use the just build "in workspace" classpath and jamvm for development. Patchlet attached. Cheers, Mark Index: .project === RCS file: /cvsroot/jamvm/jamvm/.project,v retrieving revision 1.1 diff -u -r1.1 .project --- .project 22 Dec 2005 21:36:56 - 1.1 +++ .project 23 Dec 2005 10:44:12 - @@ -56,11 +56,11 @@ org.eclipse.cdt.make.core.build.target.full - clean all + clean all install org.eclipse.cdt.make.core.build.target.auto - all + all install org.eclipse.cdt.make.core.build.location @@ -84,7 +84,7 @@ org.eclipse.cdt.make.core.build.target.inc - all + all install org.eclipse.cdt.make.core.enableCleanBuild signature.asc Description: This is a digitally signed message part ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
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
Re: Using a workspace-based VM in Eclipse
Hi, On 22 Dec 2005 12:34:42 -0700, Tom Tromey <[EMAIL PROTECTED]> wrote: > 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). > Hint taken. The necessary files are now in JamVM's cvs repository. This is your patch with a couple of changes by Raif that adds the .cvsignore files and adds an Autogen Builder to create, among other things, the configure script. Rob. > 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. > > 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 ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
>> Anyway, commit that if you like. You have rhug access, right? Mark> No I don't think I have rhug access. You do now :-) Mark> It looks like the native side gets rebuild a lot though. I guess there Mark> are some dependencies wrong since I seem to trigger a full rebuild of Mark> cacao a lot when running mauve for example. I've seen similar things on occasion. We probably need to track them down more precisely and turn them into Eclipse PRs. The external builder support seems to leave a few things to be desired... Tom ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
Hi Tom, On Thu, 2005-12-22 at 15:53 -0700, Tom Tromey wrote: > Yeah, that one is super bogus. And, I think, not actually needed. > > Anyway, commit that if you like. You have rhug access, right? No I don't think I have rhug access. > Mark> Strangely the attach source step didn't work. I always get: > Mark> Assertion failed; Path for IClasspathEntry must be absolute > > Hmm. Did you choose Workspace... when specifying the source path? I > did... anyway, check your .log, maybe this is a bug somewhere. It happens before that. When hitting the Edit... button. I worked around it by just removing the rt.jar and readding it by hand. Then I can Edit and attach source for the classpath workspace. > Mark> Wow! That is really nice. It seems to work instantly. Edit the project > Mark> or edit classpath and on a rerun your changes are there :) > > Yup, this is why I think Eclipse is the easiest way to develop > Classpath. At least, that is true for the Java side of things. For > the native code the traditional tools are probably still in the lead. It looks like the native side gets rebuild a lot though. I guess there are some dependencies wrong since I seem to trigger a full rebuild of cacao a lot when running mauve for example. Cheers, Mark signature.asc Description: This is a digitally signed message part ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
Mark> One of the symlinks didn't work for me. Attached is a patch for the Mark> tools.jar to try and find it in some other location. Generated by Mark> eclipse of course :) Yeah, that one is super bogus. And, I think, not actually needed. Anyway, commit that if you like. You have rhug access, right? Mark> Strangely the attach source step didn't work. I always get: Mark> Assertion failed; Path for IClasspathEntry must be absolute Hmm. Did you choose Workspace... when specifying the source path? I did... anyway, check your .log, maybe this is a bug somewhere. Mark> Wow! That is really nice. It seems to work instantly. Edit the project Mark> or edit classpath and on a rerun your changes are there :) Yup, this is why I think Eclipse is the easiest way to develop Classpath. At least, that is true for the Java side of things. For the native code the traditional tools are probably still in the lead. Tom ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Re: Using a workspace-based VM in Eclipse
Hi Tom, On Thu, 2005-12-22 at 12:34 -0700, Tom Tromey wrote: > 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. One of the symlinks didn't work for me. Attached is a patch for the tools.jar to try and find it in some other location. Generated by eclipse of course :) > 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. Strangely the attach source step didn't work. I always get: Assertion failed; Path for IClasspathEntry must be absolute > 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. Wow! That is really nice. It seems to work instantly. Edit the project or edit classpath and on a rerun your changes are there :) Thanks, Mark Index: build === RCS file: /cvs/rhug/fakejdk/build,v retrieving revision 1.1 diff -u -r1.1 build --- build 22 Dec 2005 19:01:09 - 1.1 +++ build 22 Dec 2005 22:51:40 - @@ -38,7 +38,13 @@ cd $top/lib # FIXME: tools.jar # We have to merge with java-gcj-compat. -cp /usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/lib/tools.jar tools.jar +if test -f /usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/lib/tools.jar; then + cp /usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/lib/tools.jar tools.jar +elif test -f /usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/lib/tools.jar; then + cp /usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/lib/tools.jar tools.jar +else + cp /usr/lib/jvm/java-*-gcj-*/lib/tools.jar tools.jar +fi cd $top/jre/bin ln -s $classpath/install/bin/$vm java signature.asc Description: This is a digitally signed message part ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
Using a workspace-based VM in Eclipse
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. 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 ___ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath
