( Static libraries

Info Catalog ( Installing executables ( Using libtool
 3.7 Linking static libraries
 Why return to `ar' and `ranlib' silliness when you've had a taste of
 libtool?  Well, sometimes it is desirable to create a static archive
 that can never be shared.  The most frequent case is when you have a
 set of object files that you use to build several different programs.
 You can create a "convenience library" out of those objects, and link
 programs with the library, instead of listing all object files for
 every program.  This technique is often used to overcome GNU automake's
 lack of support for linking object files built from sources in other
 directories, because it supports linking with libraries from other
 directories.  This limitation applies to GNU automake up to release
 1.4; newer releases should support sources in other directories.
    If you just want to link this convenience library into programs, then
 you could just ignore libtool entirely, and use the old `ar' and
 `ranlib' commands (or the corresponding GNU automake `_LIBRARIES'
 rules).  You can even install a convenience library (but you probably
 don't want to) using libtool:
      burger$ libtool ./install-sh -c libhello.a /local/lib/libhello.a
      ./install-sh -c libhello.a /local/lib/libhello.a
      ranlib /local/lib/libhello.a
    Using libtool for static library installation protects your library
 from being accidentally stripped (if the installer used the `-s' flag),
 as well as automatically running the correct `ranlib' command.
    But libtool libraries are more than just collections of object files:
 they can also carry library dependency information, which old archives
 do not.  If you want to create a libtool static convenience library, you
 can omit the `-rpath' flag and use `-static' to indicate that you're
 only interested in a static library.  When you link a program with such
 a library, libtool will actually link all object files and dependency
 libraries into the program.
    If you omit both `-rpath' and `-static', libtool will create a
 convenience library that can be used to create other libtool libraries,
 even shared ones.  Just like in the static case, the library behaves as
 an alias to a set of object files and dependency libraries, but in this
 case the object files are suitable for inclusion in shared libraries.
 But be careful not to link a single convenience library, directly or
 indirectly, into a single program or library, otherwise you may get
 errors about symbol redefinitions.
    When GNU automake is used, you should use `noinst_LTLIBRARIES'
 instead of `lib_LTLIBRARIES' for convenience libraries, so that the
 `-rpath' option is not passed when they are linked.
    As a rule of thumb, link a libtool convenience library into at most
 one libtool library, and never into a program, and link libtool static
 convenience libraries only into programs, and only if you need to carry
 library dependency information to the user of the static convenience
    Another common situation where static linking is desirable is in
 creating a standalone binary.  Use libtool to do the linking and add the
 `-all-static' flag.
Info Catalog ( Installing executables ( Using libtool
automatically generated byinfo2html