2.2 The Parts Directory Structure

The installation process creates or adds to a parts directory structure that stores software, documentation, and information that SPM uses when compiling your product.

For DBTools.h++, the parts directory structure includes the core library and access libraries.

SPM uses the following convention to name the core library parts directory:

<rw_root>\parts\dbt<ver><osfam>

For example, given a root directory called c:\rwav, a DBTools.h++ version number of 4.0.1, and a Windows NT platform, the core library parts directory is named:

c:\rwav\parts\dbt0401w

Table 5 explains how the directory is organized.

Table 5 -- Organization of the core library parts directory structure

SPM uses the following convention to name the access library parts directories:

<rw_root>\parts\<libtype><ver><osfam>

For example, given a root directory called c:\rwav, a DBTools.h++ version number of 4.0.1, and a Windows NT platform, the Informix access library is named:

c:\rwav\parts\inf0401w

Each access library has a separate parts directory that holds its source code and header files, including its <libtype>envh.h and <libtype>sysh.h files.

Table 6 lists each access library that Rogue Wave supports, with its <libtype> and its <incltype> mnemonics. The <libtype> mnemonic begins the name of each private access library header file; the <incltype> mnemonic begins the name of each public access library header file. For most libraries, they are the same

Table 6 -- Possible values for <libtype> and <incltype>

©Copyright 2000, Rogue Wave Software, Inc.
Contact Rogue Wave about documentation or support issues.