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

Appendix B lists the mnemonics for all the compilers and operating systems that Rogue Wave supports. SPM appends version numbers to the mnemonics for your compiler and operating system. Section 2.5 describes build types.

Table 6 -- Organization of the workspaces directory structure

Directory	Description
`\docs`	Tools.h++ readme file.
`\lib`	Tools.h++ library.¹
`\config`	Workspace configuration data.
`\buildloc`	Build implementation workspace.
`\rw`	Header files for Tools.h++.
`\rw\stdex`	Tools.h++ extensions to the Standard C++ Library.
`\examples`	Rogue Wave product examples.
`\examples\tls<ver><osfam>`	Tools.h++ examples.²

¹ 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 examples.