require ExtUtils::Liblist;
ExtUtils::Liblist::ext($self, $potential_libs, $Verbose);
-llib1 -llib2
-llib3
and prints out lines suitable for inclusion in an extension Makefile. Extra
library paths may be included with the form
-L/another/path
this will affect the searches for all subsequent libraries.
It returns an array of four scalar values: EXTRALIBS, BSLOADLIBS, LDLOADLIBS, and LD_RUN_PATH. Some of these don't mean anything on VMS and Win32. See the details about those platform specifics below.
Dependent libraries can be linked in one of three ways:
ext()
which is executed under
VMS differs from the Unix-OS/2 version in several
respects:
-l
and -L
prefices used by Unix linkers. If neither prefix is present, a token is considered a directory to search if it is in fact a directory, and a library to search for otherwise. Authors who wish their extensions to be portable to Unix or
OS/2 should use the Unix prefixes, since the Unix-OS/2 version of ext()
requires them.
ext()
looks for files named
libshr and librtl; it also looks for liblib and liblib to accomodate Unix conventions used in some ported software.
In general, the
VMS version of ext()
should properly handle input from extensions originally designed for a Unix or
VMS environment. If you encounter problems, or discover cases where the search could be improved, please let us know.
ext()
which is executed under Win32 differs
from the Unix-OS/2 version in several respects:
-l
and -L
prefices used by Unix linkers. -lfoo
specifies the library foo.lib
and -Ls:ome\dir
specifies a directory to look for the libraries that follow. If neither
prefix is present, a token is considered a directory to search if it is in
fact a directory, and a library to search for otherwise. The $Config{lib_ext}
suffix will be appended to any entries that are not directories and don't already have the suffix. Authors who wish their extensions to be portable to Unix or
OS/2 should use the Unix prefixes, since the Unix-OS/2 version of ext()
requires them.
$potential_libs
is empty, the return value will be empty. Otherwise, the libraries
specified by $Config{libs}
(see Config.pm) will be appended to the list of $potential_libs
. The libraries will be searched for in the directories specified in $potential_libs
as well as in $Config{libpth}
. For each library that is found, a space-separated list of fully qualified
library pathnames is generated. You may specify an entry that matches /:nodefault/i
in
$potential_libs
to disable the appending of default libraries found in $Config{libs}
(this should be only needed very rarely).