Re: Eclipse
Mark Wielaard wrote: Hi, On Sun, 2003-11-30 at 19:23, Victor Niebla wrote: Hi all, has someone succeded on building and using Eclipse with Free Vm (like sablevm or kaffe) + Classpath ??? Sure. It works with most of the free runtimes now. You have your choice of: - mono + ikvm.net http://weblog.ikvm.net/PermaLink.aspx/894943be-451e-4d6c-a692-77119eb02d06 (2.1 only as far as I know, but IKVM.NET follows GNU Classpath quite closely so getting 3.0M4 working should not be that difficult.) - kaffe Kaffe from CVS (will become 1.1.3 in one/two weeks) can run Eclipse 2.1 out of the box. 3.0M4 needs some patches (that might or might not make it for 1.1.3): http://www.kaffe.org/pipermail/kaffe/2003-October/044313.html Of course kaffe is as interested in new hackers as any other VM to help us push the treshold for free java runtimes a little higher [1]. ;) The earnest work takes place on the kaffe mailing list, the chit-chat is happening on #kaffe on irc.freenode.org. In any case, if someone would like to contribute to any of the free VMs, be it kaffe, wonka, sablevm, etc. please make sure that you meet some clean-room conditions as outlined here: http://www.kaffe.org/pipermail/kaffe/2003-November/044406.html cheers, dalibor topic [1] The wishlist for the next versions can be found here: http://www.kaffe.org/pipermail/kaffe/2003-November/044431.html Progress is happening gradually, and could happen faster if we had more volunteers [2] ;) [2] Especially DocBook, Ant, Maven & Tomcat savvy volunteers, as we plan to start using kaffe releases soon for documentation generation and the website: http://www.kaffe.org/pipermail/kaffe/2003-November/044525.html http://www.kaffe.org/pipermail/kaffe/2003-November/044528.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eclipse
Dalibor Topic wrote: Mark Wielaard wrote: Hi, On Sun, 2003-11-30 at 19:23, Victor Niebla wrote: Hi all, has someone succeded on building and using Eclipse with Free Vm (like sablevm or kaffe) + Classpath ??? Sure. It works with most of the free runtimes now. You have your choice of: - mono + ikvm.net http://weblog.ikvm.net/PermaLink.aspx/894943be-451e-4d6c-a692-77119eb02d06 (2.1 only as far as I know, but IKVM.NET follows GNU Classpath quite closely so getting 3.0M4 working should not be that difficult.) - kaffe Kaffe from CVS (will become 1.1.3 in one/two weeks) can run Eclipse 2.1 out of the box. 3.0M4 needs some patches (that might or might not make it for 1.1.3): http://www.kaffe.org/pipermail/kaffe/2003-October/044313.html Of course kaffe is as interested in new hackers as any other VM to help us push the treshold for free java runtimes a little higher [1]. ;) The earnest work takes place on the kaffe mailing list, the chit-chat is happening on #kaffe on irc.freenode.org. In any case, if someone would like to contribute to any of the free VMs, be it kaffe, wonka, sablevm, etc. please make sure that you meet some clean-room conditions as outlined here: http://www.kaffe.org/pipermail/kaffe/2003-November/044406.html cheers, dalibor topic Kaffe works with Classpath classes or his own implementation of the Java API ??? And...What are the main diferences between Kaffe, Wonka and SableVM? Thx -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eclipse
Hola Victor, Victor Niebla wrote: Kaffe works with Classpath classes or his own implementation of the Java API ??? It now uses GNU Classpath for a major part of the class library, while some parts still need to be switched over. We decided to do a gradual transition to GNU Classpath, instead of switching over completely at once. The reason was that we know all code is buggy, and doing the transition gradually helps us discover & fix previously unknown bugs in GNU Classpath for the benefit of both the kaffe & GNU Classpath communities. It's much easier to spot a bug when you know that just a few classes changed last week. Switching over to GNU Classpath is a massive undertaking, and I'd welcome volunteers helping us do the switch faster. The next stable release of kaffe is scheduled for february, so there is still a lot of work to do, if we want to be 'mostly pure GNU Classpath' by then. And...What are the main diferences between Kaffe, Wonka and SableVM? Kaffe: Has a fast jitter on many platforms. Ported to just about anything that has a 32 or 64 bit CPU. Has a working AWT. Has JAXP. Has sound. Has working regular expression support. Has a partial JVMPI implementation. Works for non-trivial applications, like running tomcat4[1] or eXist[2]. Is under heavy development[3]. But as I'm biased, I'll give the others more space ;) Wonka: Very cool VM for embedded systems. From the web-page[4]: "Wonka is ACUNIA's cleanroom Virtual Machine for the Java™ language. It is extremely portable and self-contained, and can optionally be used with its own real-time executive (OSwald™) to provide a complete solution for embedded devices. The Wonka Virtual Machine is fully Java2™ compatible and the Wonka class libraries include all the classes needed to support the OSGi framework, as well as other popular mechanisms for distributed computing such as Jetty and Castor. Wonka comes with a high-performance lightweight AWT (Rudolph™) suitable for any memory-mapped or framebuffer display. Or you can plug in your own implementation, or run with no AWT at all (e.g. in a "headless'' system). The choice is yours." SableVM: Very cool research project. From the web-page[5]: " SableVM implements many innovative techniques including: * 3 flavors of threaded interpretation (switched, threaded and inlined), * bidirectional object layout, * spinlock-free thin locks, * sparse interface vtables, * low-cost maps for precise garbage collection. SableVM is able to run many applications and benchmarks, including multi-threaded programs, but it is limited by the current state of the class libraries, and lacks VM support for some class library features. SableVM is known to reliably run non-trivial applications like SableCC 2.17.3 and Soot 1.2.3, among many others. SableVM has been ported to the following 8 architectures under Debian GNU/Linux: alpha, arm, i386, ia64, m68k, powerpc, s390, sparc. It is also known to work on FreeBSD/i386, Mac OS X and a few others. Because of the ease of doing a new port - a number of new ports is planned." hope this helps. If you want to help fill in the gaps in missing free java functionality, consider helping out with the GNU Classpath project. One of the best ways to do that is to help with the kaffe transition to GNU Classpath, of course ;) cheers, dalibor topic [1] http://www.kaffe.org/~robilad/tomcat-4.1.27-screenshot.png [2] http://www.kaffe.org/~robilad/eXist-0.9.2-screenshot.png [3] http://www.kaffe.org/~robilad/loc.png [4] http://www.acunia.com/wonka/001_about.php [5] http://www.sablevm.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eclipse
Hi!
Web site needs updating. Some week ago we switched our development
version (almost bugfree) called "STAGING" to 0.06 Classpath.
As the 0.07 Classpath has just been released - we hope to get it
working in few days.
On Mon, 2003-12-01 at 06:39, Dalibor Topic wrote:
> SableVM: Very cool research project. [...]
As for the "research" part - SableVM is first meant to be robust and
practically usable JVM. A *real* JVM. The research part is meant to be
done on a spec-compatible, standard conforming, (let me repeat) *real*
JVM. It means there's no place for sacrifying the things that are of
interest of the JVM users because of research goals. More the other way.
So in summary - instead (or along) of working on so called research
stuff we're trying to get done things like:
* retargettable (portable) SableJIT (x86, ppc currently and maybe sparc)
* getting new classpath working w/ SableVM
* getting missing JNI/Reflection stuff in place so that we could be...
* getting ex. Eclipse working :)
* getting it working on more platforms (HPPA port took 25 minutes ;-)
Probably the most valuable thing of SabelVM having "research project"
roots - for Free Software community - is that it has absolutely clean
and understandable code. Just take a look! :)
We have daily SVN (Subversion) snapshots and publicly accessible
Subversion repository.
See http://sablevm-shot.dyndns.org/ for snapshots and INSTALL.txt
See www.sablevm.org for details, see mailing lists or #sablevm channel
on irc.{debian|sablevm}.org
Cheers,
Grzegorz B. Prokopski
PS: Forget about using current debian package for now ;-) I'll get it
updated once new SableVM release is out (few weeks, I think)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eclipse
Grzegorz B. Prokopski wrote: We have daily SVN (Subversion) snapshots and publicly accessible Subversion repository. See http://sablevm-shot.dyndns.org/ for snapshots and INSTALL.txt The machine died, so *.tar.gz snapshots will be unavailable for a short while (a day or two), but everything is not lost, if you want a snapshot. Simply "apt-get install subversion", then you can get snapshots of "staging" code with: $ svn co svn://svn.sablevm.org/sablevm/trunk/staging sablevm $ svn co svn://svn.sablevm.org/sablevm-classpath/trunk/staging sablevm-classpath $ cd sablevm $ ./autogen.sh $ cd ../sablevm-staging $ ./autogen.sh $ cd .. That's it. From there, if you want to build sablevm, you can follow David Belanger's instructions in: http://sourceforge.net/mailarchive/forum.php?thread_id=3519087&forum_id=4154 Note that to get David's build_classpath script, you should type the following: $ svn cat svn://svn.sablevm.org/developers/belanger/sandbox/sablejit-classpath/bin/build_classpath > build_classpath $ chmod u+x build_classpath If you modify sablevm or sablevm-classpath, you can extract a patch file by doing the following: $ svn info ## please include the output of "svn info" in your message to the ## sablevm-devel mailing list. $ svn diff > patchfile ## attach patchfile to your message to the mailing-list Have fun! Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eclipse
Etienne Gagnon wrote: $ svn co svn://svn.sablevm.org/sablevm/trunk/staging sablevm $ svn co svn://svn.sablevm.org/sablevm-classpath/trunk/staging sablevm-classpath Oops!! Instead, this should be: $ svn co svn://svn.sablevm.org/sablevm/branches/staging sablevm $ svn co svn://svn.sablevm.org/sablevm-classpath/branches/staging sablevm-classpath Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kaffe in testing
I just sent a 1.1.2 upload into incoming. Lets see what the various platform builds make of it. On Wednesday 12 November 2003 14:59, Dalibor Topic wrote: > Those build failures should have been fixed in 1.1.2. They were mostly > introduced by the new gcc version being more strict about bad code than > versions before ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kaffe in testing
I just sent a 1.1.2 upload into incoming. Lets see what the various platform builds make of it. On Wednesday 12 November 2003 14:59, Dalibor Topic wrote: > Those build failures should have been fixed in 1.1.2. They were mostly > introduced by the new gcc version being more strict about bad code than > versions before ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
