2.5 Build Types

Build types are shown as buildtype in this manual. They are used in the workspaces directory structure (described in Section 2.3) and in library names (described in Section 2.4).

Build types use the following encoding scheme:

build#+binding+suffix

Table 9 explains this scheme.

Table 9 -- Build type encoding

Code	Meaning
`build#`	The build number. Possible build type numbers for this product and the build that they specify are: 4 = no stdlib, multithread, no debugging features 7 = no stdlib, multithread, symbolic debugging and assertions 12 = stdlib, multithread, no debugging features 15 = stdlib, multithread, symbolic debugging and assertions Note: build types 0, 3, 8, and 11 are not supported with Threads.h++ since all build types must be multi-threaded.
`binding`	The library binding: `s` = static `d` = dynamic (DLL) /shared
`suffix`	A user-defined library name suffix used to distinguish custom build configurations. By default, `suffix` is blank. The SPM online help explains how to add or edit customized build configurations.

For example, if you have a static, multithreaded library with symbolic debugging and assertions, the build type is:

7s

You could choose to give the same library a user-defined library name suffix such as _test, as in this example:

7s_test