Build Tag Conventions

The following summary tables describe the build tag naming conventions supported by RCB.

Supported Conventions

RCB supports three build tag naming conventions, as shown in Table 20.

Table 20. RCB build tag naming conventions

Convention	Description
SPM	This naming convention originated with Software Parts Manager (SPM), the predecessor to RCB. It is still the default naming convention.
RCB	A system of one-letter codes to indicate certain build options. Its advantage is concise component names. Its drawback is the need to remember the codes. The codes are explained Codes used in the short RCB build tag convention.
Verbose RCB	A long but clear sequence of strings, delimited by underscores, for indicating a component’s build characteristics.

The RCB Convention

Table 21 lists the codes used in the RCB convention.

Table 21. Codes used in the short RCB build tag convention

Code	Meaning
m	Multithreaded build
s no code	Static binding Dynamic binding (also called shared or DLL)
d no code	Debugging build Release build

Build Tags

Table 22 summarizes the build tags created by the different conventions, based on the build’s naming convention selection.

For verbose build tags associated with Standard Library selection, see Table 23.

Table 22. Summary of build tags

Build Options			Build Tags
Dynamic	Threads	Debug	RCB¹	Verbose RCB²	SPM
N	Y	N	ms	Win32ThrLib_Static_Release	12s
Y	Y	N	m	Win32ThrLib_Dynamic_Release	12d
N	Y	Y	msd	Win32ThrLib_Static_Debug	15s
Y	Y	Y	md	Win32ThrLib_Dynamic_Debug	15d

¹The values for the RCB convention assume use of the vendor standard library.

²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.

Table 23. Verbose RCB Standard Library Options

Standard Library	Build Tag
GCC	_GCCStdLib
HP	_HPStdLib
IBM	_IBMStdLib
Microsoft	_MicrosoftStdLib
Sun	_SunStdLib