This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Building the GTK peers...
Norman Hendrich a écrit :
>
> First of all, thanks for your pointers, Tom and Mark.
> Here is the final part of my AWT adventure...
>
> Norman> "cannot load AWT Toolkit: gnu.java.awt.peer.gtk.GtkToolkit"
> Norman> ... <stack trace deleted>
> Norman> I seem to remember that there was some magic involved to
> Norman> getting either the gtk or the Xlib peers built.
>
> Tom > Can it even be done? I don't remember the last time I tried it.
>
> Yes, the peers can be built (see below). But they don't really work yet...
>
> Mark> The default awt toolkit is wrong in gcj it is either
> Mark> gnu.awt.gtk.GtkToolkit or gnu.awt.xlib.XToolkit. You should be able to
> Mark> set the AWT toolkit used with -Dawt.toolkit=gnu.awt.gtk.GtkToolkit.
>
> Yes, -Dawt.toolkit=gnu.awt.gtk.GtkToolkit works, after building it.
> Fixing the wrong default property should be easy for someone with
> write access...
>
> ---
> All in all, it looks like progress with AWT and the Gtk peers requires
> people with knowledge in four areas: Java, AWT, Gtk, and "automake"...
> This certainly reduces the number of applicants :-(
>
> Perhaps someone of the automake wizards could prepare infrastructure
> in Makefile.am, similar to the xlib stuff already there, so that
> bold souls could just enable Gtk during configuration?
>
> - Norman
It seems like we did similar jobs last hours.
I have reactivated the "--enable-java-awt=gtk" configure option.
It now builds libgcjgtk.* with the same flavor as libgcjx.* getting
built with "--enable-java-awt=xlib" configure option.
I definitely want to contribute this patch, but I think it may need
a few adjustements before actual check in (for example, I don't know
how to check at configure time the availability of gtk).
What do you gcc expert think of this solution ?
May I contribute now and let the autoconf expert fill the gap ?
Or can someone help me finishing the autoconf part before ?
Laurent Bardet