Fink shlibs policy allows symlinks in the shlibs splitoff: libGlw.dylib symlink goes in the -dev splitoff libGlw.a archive goes in the -dev splitoff
libGlw.1.dylib symlink goes in the -shlibs splitoff libGlw.1.0.dylib goes in the -shlibs splitoff. No compatibility problems at all. Peter David R. Morrison wrote: > Jack, > > What's important for linking on OS X is not the filename, but rather > the "install_name" of the shared library. You can check the > install_name with "otool -L foo.dylib". > > Most likely, in the older version the filename of the library was > libGLw.1.0.dylib but the install_name was libGLw.1.dylib (with a > symlink put in place to relate the two). Now in the simpler version, > that intermediate step is skipped and both the filename and > install_name are libGLw.1.dylib. So there is no problem. > > -- Dave > > P.S. In case you are curious about the reason for this, on Linux (and > the ELF filesystem in general), there is no versioning of libraries, > so somebody (perhaps the libtool project) invented the "extra decimal > plus symlink" way of enforcing versioning on libraries. For many > years, this same method was copied over to OS X, but it was unneeded > because OS X has true versioning of libraries. The most recent > versions of libtool skip that "extra decimal" step for OS X, so I'm > guessing that what happened is that the upstream authors have updated > their libtool. > > On Dec 31, 2008, at 9:31 PM, Jack Howarth wrote: > >> I was considering updating the mesa-libglw package to the >> new Mesa 7.2 stable release but I am running into a shared library >> issue that has me a tad baffled. The Mesa 7.2 release now builds >> a libGLw.1.0.dylib with libGLw.1.dylib and libGLw.dylib symlinks. >> In Mesa 7.0.x this was a libGLw.1.dylib with only a libGLw.dylib >> symlink. What in the devil am I supposed to do in this situation? >> The libraries should be backward compatible but the shlibs package >> will have a libGLw.1.0.dylib while programs that were previously >> built against the libGLw from Mesa 7.0.2 will be linked to >> libGLw.1.dylib (which can't be in the shlibs as a symlink >> according to fink). >> Has this situation ever occured before? Any advice would >> be welcome. >> Jack -- Peter O'Gorman http://pogma.com ------------------------------------------------------------------------------ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel
