backwards-compatible linking to system libraries
backwards-compatible linking to system libraries
- Subject: backwards-compatible linking to system libraries
- From: Nathan Lamont <email@hidden>
- Date: Mon, 27 Oct 2003 18:47:50 -0500
When linking to a standard library in /usr/lib, say libfoo.dylib, by
adding -lfoo to the linker flags, it seems that the executable is
linked to a specific version number of that library, say
libfoo.0.1.2.dylib. With symlinks, this is made forward compatible, but
it is not backwards compatible.
In other words, Mac OS X 10.2 may have only libfoo.0.1.2.dylib, and Mac
OS X 10.3 may have the newer libfoo.0.2.0.dylib and a symlink
libfoo.0.1.2.dylib pointing to the newer version, so apps that link to
the older version will still work. But if I build an app on 10.3,
linking to libfoo, it won't work on 10.2, because it won't be able to
find the newer and differently named libfoo0.2.0dylib.
Is there a backwards compatible way of linking to a standard library,
or is this simply not supposed to be done? Or have I misunderstood the
situation?
< Nathan Lamont / www.biggerplanet.com >
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.