[kaffe] --disable-native-awt semantics

[Dalibor Topic]

Hi all,

Supreet has been kind enough to raise this issue as #32 in Kaffe's bug
tracker, at http://www.kaffe.org/cgi-bin/bugzilla/show_bug.cgi?id=32

I'd like to hear some feedback what solution you'd like, i.e. what
--disable-native-awt should do, or if it should be there at all.

I am not sure what the best solution would be:

a) --disable-native-awt disables all AWT backends i.e. passes --disable-gtk-awt
to gnu classpath's build.

b) --disable-native-awt is removed, since it does not disable all AWT backends,
it's a convenience switch that does not work as conviently as it should

c) add the switches from Classpath's configure to Kaffe's configure:

  --disable-gtk-peer      compile GTK native peers (disabled by --disable-jni)
                          default=yes

  --enable-gtk-cairo      build the cairo Graphics2D implementation on GTK
                          default=no
  --enable-qt-peer        compile Qt4 native peers (disabled by --disable-jni)
                          default=no
and drop --disable-native-awt

Of course, better ideas d-z are also welcome. ;)

cheers,
dalibor topic