From: Bruno Haible <bruno@clisp.org>
Date: Tue, 6 May 2025 15:00:51 +0000 (+0200)
Subject: doc: Explain how to specify library dependencies.
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=40bd49b6119f581d6604d1c67e4ccf7cfc520602;p=thirdparty%2Flibtool.git

doc: Explain how to specify library dependencies.

* doc/libtool.texi (Link mode): Explain how to specify dependencies to
already installed libraries.
---

diff --git a/doc/libtool.texi b/doc/libtool.texi
index 60ddab7a1..ba64245eb 100644
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -1708,6 +1708,11 @@ Pass a linker-specific flag directly to the linker.
 Pass a link-specific flag to the compiler driver (@code{CC}) during linking.
 @end table
 
+Note: When the output file shall depend on an installed library, you
+cannot specify the library name as @code{@var{dir}/lib@var{name}.a} or
+@code{@var{dir}/lib@var{name}.so} as part of the @var{mode-args}.
+Instead, pass the arguments @code{-L@var{dir}} and @code{-l@var{name}}.
+
 If the @var{output-file} ends in @file{.la}, then a libtool library is
 created, which must be built only from library objects (@file{.lo} files).
 The @option{-rpath} option is required.  In the current implementation,