libtool: Issues

1 
1 1.2 Implementation issues
1 =========================
1 
1 The following issues need to be addressed in any reusable shared library
1 system, specifically libtool:
1 
1   1. The package installer should be able to control what sort of
1      libraries are built.
1 
1   2. It can be tricky to run dynamically linked programs whose libraries
1      have not yet been installed.  'LD_LIBRARY_PATH' must be set
1      properly (if it is supported), or programs fail to run.
1 
1   3. The system must operate consistently even on hosts that don't
1      support shared libraries.
1 
1   4. The commands required to build shared libraries may differ wildly
1      from host to host.  These need to be determined at configure time
1      in a consistent way.
1 
1   5. It is not always obvious with what prefix or suffix a shared
1      library should be installed.  This makes it difficult for
1      'Makefile' rules, since they generally assume that file names are
1      the same from host to host.
1 
1   6. The system needs a simple library version number abstraction, so
1      that shared libraries can be upgraded in place.  The programmer
1      should be informed how to design the interfaces to the library to
1      maximize binary compatibility.
1 
1   7. The install 'Makefile' target should warn the package installer to
1      set the proper environment variables ('LD_LIBRARY_PATH' or
1      equivalent), or run 'ldconfig'.
1