On Sunday, July 02, 2000 at 12:13, Tom Tromey wrote:
> Oskar> I've been spending some time porting Classpath AWT to gcj. I
> Oskar> have rewritten the JNI GTK peer to CNI, and made sure the java
> Oskar> files compile with gcj.
>
> This is definitely interesting to us.
> I'm curious, though -- did you try the JNI peers at all?
> I wonder if those would work. Gcj has JNI now, but it hasn't been
> extensively tested.
No, I started with converting the JNI code to CNI. It wasn't just
a matter of making C++ methods of the JNI C functions, because
the Classpath uses a different way of storing native pointers.
Pointers are associated with objects and kept in some external
hashtable, while RawData is the natural way in CNI.
> There's been some talk of coordinating with the Gtk people to make Gtk
> objects and Java objects compatible. Then we wouldn't need either CNI
> or JNI -- we could just call Gtk objects directly. I don't know if
> this work will really happen or not, though.
If I understand you correctly - does this means another layer
between AWT and the native/C Gtk functions? AFAIK there is
already one project porting Gtk to gcj/CNI, but there is
little progress.
Oskar Liljeblad ([EMAIL PROTECTED])
