Apache OpenOffice (AOO) Bugzilla – Issue 65011
library versioning scheme does not match platform concept
Last modified: 2013-07-30 02:37:53 UTC
In http://developer.apple.com/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/VersionInformation.html Apple describes the concept behind library versioning on Mac OS X. Neither the libaries build with OOo (if versioned), nor the SAL_MODULENAME_WITH_VERSION macro comply to this concept: ~/OpenOffice.org 2.0.app/Contents/openoffice.org/program olli$ ls *.dylib.* libcppu.dylib.3 libicuuc.dylib.26.0 libsndfile.dylib.1 libcppuhelpergcc3.dylib.3 libjvmaccessgcc3.dylib.3 libsndfile.dylib.1.0.9 libicudata.dylib.26 libjvmfwk.dylib.3 libstore.dylib.3 libicudata.dylib.26.0 libportaudio.dylib.0 libuno_cppu.dylib.3 libicui18n.dylib.26 libportaudio.dylib.0.0.18 libuno_cppuhelpergcc3.dylib.3 libicui18n.dylib.26.0 libreg.dylib.3 libuno_sal.dylib.3 libicule.dylib.26 librmcxt.dylib.3 libuno_salhelpergcc3.dylib.3 libicule.dylib.26.0 libsal.dylib.3 libicuuc.dylib.26 libsalhelpergcc3.dylib.3
Beside moving the version information before the "dylib", another interesting project would be to make URE/UDK become a Mac OS X style framework.
The backwards-compatibility links libcppu.dylib.3, libcppuhelpergcc3.dylib.3, libsal.dylib.3, and libsalhelpergcc3.dylib.3 (superseded by libuno_XXX variants in issue 20747 integrated in OOo 2.0) are probably not needed at all on Mac OS X (unless there can be C/C++ UNO components running on Mac OS X that have been built pre OOo 2.0).
Since we just increased the official baseline to Mac OS X 10.4 aka Tiger, we dropped binary compatibility anyway, so I agree those links can be removed. Maybe those links should limited to a positive list anyway.
Reset assignee on issues not touched by assignee in more than 1000 days.