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 A lists the mnemonics for all the compilers and operating systems that Rogue Wave certifies. SPM appends version numbers to the mnemonics for your compiler and operating system. Section 2.6 describes build types.

Table 6 -- Organization of the workspaces directory structure

Directory	Description
`docs`	Tools.h++ Professional readme file.
`lib`	Tools.h++ Professional libraries.¹
`config`	Workspace configuration data.
`buildloc`	Build implementation workspace.
`rw\toolpro`	Header files for Tools.h++ Professional.²
`examples`	Rogue Wave product examples.
`examples\tpr<ver><osfam>`	Tools.h++ Professional examples.³

1	A build of Tools.h++ Professional creates two or three C++ libraries, depending on how completely your system satisfies dependency requirements (see Section 1.3, "Product Dependencies,"). For MSVC, the `lib` directory may also contain `.pdb` files, which contain information about debug versions of the libraries.
2	For backwards compatibility, the `rw` directory for now contains the directories `net`, `inet`, and `orb`, corresponding to the products from which Tools.h++ Professional was created. These directories contain files that `#include` the header files in `rw\toolpro`.
3	For MSVC, this directory may also contain `.pdb` files, which contain information about debug versions of the examples.

The following illustration shows the examples\tpr<ver><osfam> directory tree:

examples
   \tpr<ver><osfam>
      \inet
      \net
      \orbs

Some of the examples require command-line arguments. See the README file in each examples directory for relevant usage information.