Hi Tom, On Mon, 2006-07-31 at 09:52 -0400, Thomas Fitzsimmons wrote: > > On Fri, 2006-07-28 at 19:41 -0400, Thomas Fitzsimmons wrote: > >> I committed this patch to make the peer libraries versionless. This is > >> good > >> practice for dlopen'd libraries. In the case of libjawt.so which is meant > >> to be > >> linked to, making it versionless gives it the SONAME of "libjawt.so", > >> which > >> makes it binary compatible with Sun's library. > > > >> 2006-07-28 Thomas Fitzsimmons <[EMAIL PROTECTED]> > >> > >> * native/jawt/Makefile.am (libjawt_la_LDFLAGS): Add > >> -avoid-version. > >> * native/jni/gtk-peer/Makefile.am (libgtkpeer_la_LDFLAGS): > >> Likewise. > >> * native/jni/midi-alsa/Makefile.am (libgjsmalsa_la_LDFLAGS): > >> Likewise. > >> * native/jni/midi-dssi/Makefile.am (libgjsmdssi_la_LDFLAGS): > >> Likewise. > > > > There was no patch attached (done so now). Also, would you recommend > > this for the release branch? > > Yes, along with this one: > > 2006-07-31 Thomas Fitzsimmons <[EMAIL PROTECTED]> > > * native/jni/qt-peer/Makefile.am (libqtpeer_la_LDFLAGS): Add > -avoid-version.
OK, both added to the release and generics branch. Why do we only need this for these libraries? Would it be an idea to just do this for CLASSPATH_MODULES as defined in configure.ac or do some core native jni libs need to be versioned? Cheers, Mark