Hi,
applications that use the AWT Native Interface refer to "libjawt.so".
For binary compatibility with other AWT Native Interface implementations
our .so must be named the same.
Note to packagers: libjawt.so should be installed in VM-specific
directory rather than directly in /usr/lib. Proprietary VMs put their
libjawt.so implementations in VM-specific directories but search
/usr/lib first. If GNU Classpath's libjawt.so is installed in /usr/lib
it will create problems for people using a proprietary VM to run AWT
Native Interface apps.
I committed the attached patch.
Tom
2006-05-26 Thomas Fitzsimmons <[EMAIL PROTECTED]>
* native/jawt/Makefile.am (nativeexeclib_LTLIBRARIES): Rename
libjawtgnu.la libjawt.la.
Index: native/jawt/Makefile.am
===================================================================
RCS file: /sources/classpath/classpath/native/jawt/Makefile.am,v
retrieving revision 1.5
diff -u -r1.5 Makefile.am
--- native/jawt/Makefile.am 25 May 2006 15:29:36 -0000 1.5
+++ native/jawt/Makefile.am 26 May 2006 16:12:00 -0000
@@ -1,11 +1,7 @@
-nativeexeclib_LTLIBRARIES = libjawtgnu.la
+nativeexeclib_LTLIBRARIES = libjawt.la
-libjawtgnu_la_SOURCES = jawt.c
-libjawtgnu_la_LIBADD = $(top_builddir)/native/jni/gtk-peer/libgtkpeer.la
-# FIXME: libtool doesn't allow overriding SONAME, but we need to set
-# it to libjawt.so for binary compatibility.
-#
-# libjawtgnu_la_LDFLAGS = -Wl,-soname -Wl,libjawt.so
+libjawt_la_SOURCES = jawt.c
+libjawt_la_LIBADD = $(top_builddir)/native/jni/gtk-peer/libgtkpeer.la
AM_LDFLAGS = @CLASSPATH_MODULE@ @GTK_LIBS@ @PANGOFT2_LIBS@ @X_LIBS@ -lXtst
AM_CPPFLAGS = @CLASSPATH_INCLUDES@
