[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
mode=link and full path to dependent shared library?
From: |
Tim Mooney |
Subject: |
mode=link and full path to dependent shared library? |
Date: |
Thu, 6 Oct 2005 17:46:48 -0500 (CDT) |
Can someone point me to the place in the docs that explains libtool's
handling of --mode=link when a dependent shared library is specified by
full path? I'm having trouble finding it.
I'm talking about a situation like this:
/bin/sh ./libtool --tag=CXX --mode=link cxx -some_compiler_flags -o libfoo.la
-rpath /path/to/lib -version-info 16:3:1 -no-undefined foo.lo bar.lo baz.lo
/path/to/lib/libdep.so -llib2 -lc -rpath /path/to/lib
libtool should be creating libfoo.la (and both shared and archive libfoo
libraries) and should be linking against /path/to/lib/libdep.so, but it's
eliding the /path/to/lib/libdep.so from the shared library creation line.
I'm just trying to find where this behavior is discussed, so I can
understand why it's doing that.
Tim
--
Tim Mooney address@hidden
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
- mode=link and full path to dependent shared library?,
Tim Mooney <=