Michael Koch wrote:
On Fri, May 26, 2006 at 01:50:10PM -0400, Thomas Fitzsimmons wrote:
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.
This should also be mentioned in the NEWS file.
Done.
Tom
2006-05-27 Thomas Fitzsimmons <[EMAIL PROTECTED]>
* NEWS: Announce libjawtgnu.so-to-libjawt.so rename.
Index: NEWS
===================================================================
RCS file: /sources/classpath/classpath/NEWS,v
retrieving revision 1.145
diff -u -r1.145 NEWS
--- NEWS 27 May 2006 21:10:46 -0000 1.145
+++ NEWS 27 May 2006 21:13:24 -0000
@@ -1,5 +1,12 @@
New in release 0.92 (UNRELEASED)
+* libjawtgnu.so has been renamed libjawt.so for binary compatibility.
+ libjawt.so should be installed in a 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 who use a proprietary VM to run AWT Native
+ Interface applications.
* The GdkGraphics2D backend has been made the default. There is no
longer an explicit dependency on Cairo, the --enable-gtk-cairo
configure option is gone, and GTK 2.8 or higher is now required to
