2.4 Library Names

Threads.h++ C++ libraries for Unix use this encoding scheme:

libmnemonic+buildtype.ext

Threads.h++ C++ libraries for Windows use this encoding scheme:

mnemonic+buildtype.ext

Both of these schemes are explained in Table 7.

Table 7 -- Library name encoding

Code	Meaning
`lib`	Indicates that this is a library. (Unix only.)
`mnemonic`	The mnemonic from one of the nine C++ libraries that constitute Threads.h++: `functor`, `functor_list`, `functor_map`, `itc`, `pointer`, `sync`, `thread`, `threxcept`, and `trace`.
`buildtype`	Indicates the build type, as explained in Section 2.5.
`ext`	Indicates the extension. For Windows static libraries and `DLL` import libraries, the extension is `lib`. For Windows `DLL`s, 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 contained within the `buildtype` to determine whether a library is static or shared.

For example, Table 8 shows the library names that result, depending on your compiler, when you build multithreaded, static libraries that provide symbolic debugging and assertions.

Table 8 -- Library names according to compiler

Tools.h++ Enterprise libraries	Library Names Resulting from a UNIX compiler	Library Names Resulting from a MSVC compiler on Windows 95/NT/ Windows 2000
`functor`	`libfunctor7s.a`	`functor7s.lib`
`functor_list`	`libfunctor_list7s.a`	`functor_list7s.lib`
`functor_map`	`libfunctor_map7s.a`	`functor_map7s.lib`
`itc`	`libitc7s.a`	`itc7s.lib`
`pointer`	`libpointer7s.a`	`pointer7s.lib`
`sync`	`libsync7s.a`	`sync7s.lib`
`thread`	`libthread7s.a`	`thread7s.lib`
`threxcept`	`libthrexcept7s.a`	`threxcept7s.lib`
`trace`	`libtrace7s.a`	`trace7s.lib`