This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: compiling java.awt with gcj
- From: Brian Jones <cbj at gnu dot org>
- To: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
- Cc: Laurent Bardet <l dot bardet at magic dot fr>, "Koecher Rainer ETR.ETB2" <Rainer dot Koecher at elinebgtraction dot at>, java at gcc dot gnu dot org
- Date: 31 Jul 2002 08:46:52 -0400
- Subject: Re: compiling java.awt with gcj
- References: <174DD27579F8A64E852EFA47236C6816013EA127@viepe-mxs0001.iserv.vads.cc><3D477C99.C6C5B3C3@magic.fr> <3D479FD9.6060704@waitaki.otago.ac.nz>
Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:
> For the CNI GTK peers which are in the libjava tree, displaying a
> frame is pretty much all that I implemented so far ;-)
>
> Others have reported some success using the JNI-based GTK peers from
> the classpath tree. In the long run CNI based peers would be better,
> because CNI is more efficient and maintainable. But it might be that
> working on the peers from the classpath tree is the best way to get
> something running quickly.
There is a lot of native code here that makes me question the
usefulness of making CNI peers that are only useful to gcj when the
JNI peers are still in need of so much work. Without code sharing or
just working on the JNI peers I fear that while gcj may gain something
here the rest of the free software vm world loses. As noted, gcj has
no trouble using the JNI peers.
Brian
--
Brian Jones <cbj@gnu.org>