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.
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 +
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 o
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
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
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/sablev
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
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
8 matches
Mail list logo