2.4 Library Names

LAPACK.h++ libraries for Unix use this encoding scheme:

lib<libtype><buildtype>.<ext>

LAPACK.h++ libraries for Windows use this encoding scheme:

<libtype><buildtype>.<ext>

Both of these schemes are explained in Table 7.

Code	Meaning
`lib`	Indicates that this is a library. (Unix only.)
`<libtype>`	Indicates the library type. `lpk` = LAPACK.h++ core library `laf` = FORTRAN library provided with LAPACK.h++
`<buildtype>`	Indicates the build type, explained in Section 2.5.
`<ext>`	Indicates the extension. For Windows static libraries and DLL import libraries, the extension is `lib`. For Windows DLLs, the extension is `dll`. For Unix, the extension naming convention varies from one platform to another. Here are some possible values: `.a` = static library (`ns.a` for AIX) `.so`, `.sl`, etc. = shared library, depending upon the platform Note: Always use the library binding character to determine whether a library is static or shared.

For example, on Unix, a static, multithreaded LAPACK.h++ core library with symbolic debugging and assertions has this library name:

liblpk7s.a

The same library built on Windows NT or Windows 95 is named:

lpk7s.lib