Rogue Wave Component Builder (RCB): Building Your Applications : PART III Appendices : Appendix A Build Tag Conventions : Build Tags
Build Tags
Table 10 summarizes the build tags created by the different conventions. Note that use of the C++ standard library is assumed in all builds, and is assumed to be based on the system native standard library.
Table 10 – Summary of build tags 
Build Options
Build Tags
Dynamic
Threads
Debug
RCB1
Verbose RCB2
SPM
N
N
N
s
_NativeStdLib
_NoThrLib_Static_Release
8s
Y
N
N
no tag
_NativeStdLib
_NoThrLib_Dynamic_Release
8d
N
N
Y
sd
_NativeStdLib
_NoThrLib_Static_Debug
11s
Y
N
Y
d
_NativeStdLib
_NoThrLib_Dynamic_Debug
11d
N
Y
N
ms
_NativeStdLib
_Win32ThrLib_Static_Release
12s
Y
Y
N
m
_NativeStdLib
_Win32ThrLib_Dynamic_Release
12d
N
Y
Y
msd
_NativeStdLib
_Win32ThrLib_Static_Debug
15s
Y
Y
Y
md
_NativeStdLib
_Win32ThrLib_Dynamic_Debug
15d
1 The values for the RCB convention assume use of the native standard library. On Solaris platforms, the option to use STLPort exists, and also results in an ‘s’ tag. Thus you could even end up with a library name having two ‘s’ tags. A static, single-threaded build of Essential Tools using STLPort would result in the library name tls<ver>-ss.so.

2 The Verbose RCB examples are based on a Windows installation, so the ones with threading enabled have _Win32ThrLib. On other systems, different threading tags are generated. One tag on most UNIX systems, for example, is _PosixThrLib. If STLPort is used on Solaris platforms, the tag _NativeStdLib would change to _STLPortStdLib.