RE: Status of BeOS x86 kaffe

[Duncan W. McQueen]

Cleanroom conditions?  Was that the statement that we didn't look at the Sun
sources?

WHat needs to be done to get those sources folded into the kaffe tree?

Thanks,
Duncan McQueen
BeKaffe

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Edouard G. Parmelan
Sent: Sunday, June 03, 2001 11:56 AM
To: Chris Nash
Cc: [EMAIL PROTECTED]
Subject: Re: Status of BeOS x86 kaffe



Chris Nash wrote:

 I saw it mentioned at kaffe.org and in the FAQ that the BeOS threading
 model is incomplete (something I noticed when the preempt.java test
 needed a ctrl+C to get past) and I checked the archives, and it seems
 to me there hasn't been any BeOS activity for about 12 months, nor is
 BeOS mentioned in the supported systems, however I can at least get
 1.0.6 to build and work except for the threading issues, and it seems
 no JIT3.

To add jit3 support for x86 BeOS, simply create the file
config/i386/beos/jit3-md.h that contains only this line:

#include i386/beos/jit-md.h

 The BeKaffe AWT group seems equally dead.

Yep, on 14 Oct 2000, Tomaso Paoletti wrote:

Tomaso For almost one year I've been developing, together with other
Tomaso developers (mainly Sim Ijskes) the AWT layer targeted to BeOS,
Tomaso under the name of Project BeKaffe (http://bekaffe.sourceforge.net).
Tomaso
Tomaso As I'm in the process of abandoning the project, due to lack of
time,
Tomaso and no one is available to take this job, I would ask you if it's
possible to
Tomaso contribute back all the sources, so that the effort does not remain
pointless
Tomaso if some other brave soul wants to take from where we're leaving.
Tomaso
Tomaso It won't require great changes to the current CVS source base,
Tomaso we have been a nice project living in separate BeOS directories :-)
Tomaso The only shared changes that come to mind is the addition of two
Tomaso unharmful lines into the configure.in and ltconfig scripts.

But I don't know if Tim have received `cleanroom conditions' (see
http://www.kaffe.org/develop.html#cleanroom) so I never download bekaffe
sources.

 Is anyone looking at the BeOS-native version at all? If so, I'd like to
 give some help - if not, it's something I'd like to give a little time
 to, at the very least to get things going again.
--
Edouard G. Parmelan
http://egp.free.fr
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.255 / Virus Database: 128 - Release Date: 5/17/2001

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.255 / Virus Database: 128 - Release Date: 5/17/2001


NetZero Platinum
No Banner Ads and Unlimited Access
Sign Up Today - Only $9.95 per month!
http://www.netzero.net

BeKaffe questions

[Duncan W. McQueen]

This is from a BeKaffe developer (Kaffe for BeOS at
 http://bekaffe.netpedia.net).  Any feedback?


Howdy- 
 
I finally figured out that one of the biggest problems with the widgets  
is the way graInitGraphics() sets the clipping region [ Arrghhh!!! Why  
didn't this occur to me two *#^*$ months ago!?!]. 
 
It would be easy to resolve this problem if we had a sort of "shadow"  
BView for each of the widgets a particular app uses. Does anyone know  
how I can get the bounding coordinates of a widget, so that I can give  
it its own little BView at the time of window creation? Maybe something  
with JNI? 
 

 

Classpath and Kaffe

[Duncan W. McQueen]

Is there any work or synchronization between Classpath and Kaffe?  Are 
there things implemented in Classpath that aren't in Kaffe, and the 
same in reverse?

Thanks,
Duncan McQueen

Re: Classpath and Kaffe

[Duncan W. McQueen]

But I am concerned with the GPL Kaffe.  Is it unfeasible to attempt a 
merge of what Classpath has done into Klasses.jar??


Duncan W. McQueen writes:
 Is there any work or synchronization between Classpath and Kaffe?  
Are 

Not really.

 Are there things implemented in Classpath that aren't in Kaffe, and 
the 
 same in reverse?

Probably (I don't know what's currently implemented in Classpath).

You could argue that the root of the problem is that Sun never
fully spec'd the JVM, because they didn't specify what the native
methods are (eg, in java.lang.Thread et.al).  So Classpath and
kaffe's "JVM API" are different.

More to the point, they were started as separate projects, and like
most separate projects, there hasn't been a lot of spontaneous
communication or coordination.

Plus, TVT needs to own the copyright to any files they sell to
customers in the custom edition. So unless Classpath was willing
to grant this right, TVT would have to rewrite everything anyway.

-Archie


___

Archie Cobbs   *   Whistle Communications, Inc.  *   http://
www.whistle.com

BeOS, Kaffe and AWT

[Duncan W. McQueen]

What needs to happen to get AWT working on BeOS?  Is this a very hard 
thing to do?  I have many applications thgat would benefit from this 
(saving rebooting to run them), and I was wondering how it could 
happen.

Thanks,
Duncan McQueen