David R. Morrison wrote:
[]
> 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
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
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.
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
