2.4 Library Names

DBTools.h++ libraries for UNIX use this encoding scheme:

lib<libtype><buildtype>.<ext>

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

<libtype><buildtype>.<ext>

Both of these schemes are explained in Table 8.

Code	Meaning
`lib`	Indicates that this is a library. (UNIX only.)
`<libtype>`	Indicates that this is either the DBTools.h++ core library (indicated by `dbt`) or an access library (indicated by one of the values listed in Table 6).
`<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: Static and dynamic are kinds of binding. Always use the library binding character, defined in Table 9, to determine whether a library is static or shared.

For example, a multithreaded, static DBTools.h++ library that provides symbolic debugging and assertions, built using a UNIX compiler, is named:

libdbt7s.a

The same library built using a Windows compiler is named:

dbt7s.lib

A compatible ODBC access library built using a Windows compiler is named:

odb7s.lib