2.3 The Workspace Directory Structure

The build process creates or adds to a workspaces directory structure that is used to store library, object, and header files after being built with SPM. SPM uses the following convention to name the workspace:

<rw_root>\workspaces\<OS+ver>\<COMPILER+ver>\<buildtype>

For example, if the root directory is c:\rwav, the platform is Windows NT 4.0, the compiler is MSVC 6.0, and the library build type is 7s, the workspace is named:

c:\rwav\workspaces\WINNT4\MSVC60\7s

Table 7 shows the directories created by SPM for each build type. SPM also appends version numbers to the mnemonics for your compiler and operating system. See Section 2.5 for a description of build types, and Appendix A for the mnemonics for all supported compilers and operating systems.

Table 7 -- Organization of the workspaces directory structure for each build

Directory	Description
`\buildloc`	Build implementation workspace.
`\config`	Workspace configuration data.
`\docs`	DBTools.h++ `readme` file.
`\lib`	DBTools.h++ libraries.¹
`\rw\db`	DBTools.h++ and *DecimalPortable*-related header files.
`\rw\db\dbsrc`	Private header files used for access library compilation.
`\rw\db\<incltype>src`	Public access library header files. Table 6 lists possible values for `<incltype>`.
\rw	Tools.h++ header files.
`\examples`	Rogue Wave product examples.
`\examples\dbt<ver><osfam>`	DBTools.h++ tutorials and makefiles.²

¹	For MSVC, the `lib` directory also contains the `.pdb` file, which contains information about debug versions of the library.
²	For MSVC, this directory also contains `.pdb` files, which contain information about debug versions of the tutorials.