Disable xlib peers by default, add --enable-java-awt configure option

Bryce McKinlay bryce@albatross.co.nz
Wed Feb 21 03:30:00 GMT 2001


Jeff Sturm wrote:

> > > Since others have reported problems building the xlib peers,
> > > and they really aren't in a release form yet, should they be disabled by
> > > default on the branch?

Heres a patch to do that. The idea is that you can specify a comma separated
list of peers to build in the --enable-java-awt argument

eg

--enable-java-awt=gtk
--enable-java-awt=xlib,gtk

The patch disables the xlib peers by default unless xlib is specified on the
configure cmd.

It works nicely but I'd also like to have it complain appropriatly if someone
specifies "--enable-java-awt=xlib" but doesn't have X headers installed or
whatever. It seems that the test for
"if [test "$no_x" = yes]" doesn't actually work, even though it definatly did
seem work inside an AM_CONDITIONAL previously ("--without-x" stopped libgcjx
being build).

Any ideas on that one Tom?

regards

  [ bryce ]




More information about the Java-patches mailing list