This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: compiling java.awt with gcj
- From: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
- To: Laurent Bardet <l dot bardet at magic dot fr>
- Cc: "Koecher Rainer ETR.ETB2" <Rainer dot Koecher at ElinEbgTraction dot at>, java at gcc dot gnu dot org
- Date: Wed, 31 Jul 2002 20:29:13 +1200
- Subject: Re: compiling java.awt with gcj
- References: <174DD27579F8A64E852EFA47236C6816013EA127@viepe-mxs0001.iserv.vads.cc> <3D477C99.C6C5B3C3@magic.fr>
Laurent Bardet wrote:
I wrote a simple test program which displays a window with nothing in it
and compiled it successfully. But when I tried to start the program I
got the following output on the command line:
returned
end
I guess it was for debug or test purposes. I didn't find any PR for
this. I think the two err output lines should be removed.
Can somebody with a write access do it ?
Yes, thanks for pointing that out. I checked in a patch to remove them.
that is all what happened.
With a simple test AWT program having a single frame, I got the same
output as you, and the frame is displayed.
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.
regards
Bryce.