Differences between version 8 and predecessor to the previous major change of SharedLibrary.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 8 | Last edited on Wednesday, November 10, 2004 5:59:50 pm | by PerryLorier | Revert |
| Older page: | version 7 | Last edited on Monday, October 4, 2004 3:48:58 am | by StuartYeates | Revert |
@@ -42,9 +42,9 @@
So long as you don't change the call signature of one of the functions (or what they do, in a way that would break programs), you can just bump the minor version of the library and programs using the SharedLibrary will just work. If you do change call signatures on existing functions or change their semantics, bump the version, try to recompile the programs, and check that they work correctly once they pass. Another way to make it usable is to put it in a directory refered to in your __LD_LIBRARY_PATH__ environment variable.
You may wish to use -Wl,-O1 when linking too, it will optimise the hashtables used for symbol lookup making the startup time faster.
-For more information, see Ulrich Drepper's [How to write shared libraries | http://people.redhat.com/drepper/dsohowto.pdf].
+
!! Creating a SharedLibrary using libtool(1)
libtool(1) is a package designed to assist with the creation of shared libraries. See the libtool(1) node for more information (eventually) about this program
@@ -78,4 +78,9 @@
nm /lib/libc.so.6
doesn't work, as libc is a dynamic library, however
nm --dynamic /lib/libc.so.6
will. just [FYI].
+
+!!Good external resources
+* Ulrich Drepper's [How to write shared libraries | http://people.redhat.com/drepper/dsohowto.pdf].
+* Mike Hearn's [Writing shared libraries | http://navi.cx/~mike/writing-shared-libraries.html].
+* (can't anyone come up with a unique descriptive name for this stuff?)
