Appendix B: Glossary

`<buildtype>`	A variable indicating a build type, which consists of a build number, binding type, and optional user-defined library suffix. See Chapter 2 for more information.
buildable part	A package of software that can be installed and built using the SPM configuration and build model. Parts can contain other parts. For example, the Tools.h++ library is one buildable part, and the Tools.h++ examples are another.
build profile	A combination of four common build options: static/shared, debug/not debug, single-threaded/multithreaded, with Standard C++ Library/without Standard C++ Library. One element in a configuration.
`<COMPILER>`	A variable indicating the compiler you're using.
Configuration and Build Model (CBM)	A series of Korn shell scripts that know how to determine a compiler's capabilities, generate makefiles from makefile templates, invoke `make`, and install software.
configuration	Build configuration information used by the CBM. A configuration combines the information in a build profile and an environment profile and may specify additional compile and link options.
distribution repository	A data file that contains information about the products and documentation available to SPM. SPM updates this repository when you unlock additional products.
environment profile	A specific operating system and compiler combination. One element in a configuration.
`<OS>`	A variable indicating your operating system.
`<osfam>`	A variable indicating your operating system family: `w` for Windows, `u` for Unix, and `o` for OS/2.
`partmgr`	An application with a graphical user interface that installs Rogue Wave software purchases, invokes the mechanism that builds installed software, and displays product marketing literature.
parts directory structure	A directory hierarchy containing the sources for a buildable software part.
`<rw_root>`	A variable indicating the name you gave your Rogue Wave root directory. For example: `c:\rwav`.
Software Parts Manager (SPM)	A tool for selecting and managing Rogue Wave products (parts). SPM has two components: a set of configuration and build model scripts and the `partmgr` application.
`<ver>`	A variable indicating the version number of an operating system, compiler, or product.
working repository	A data file describing configurations and the state of an SPM installation site-which products have been installed and which parts have been built.
workspace directory structure	A platform-specific directory hierarchy containing built, ready-to-use software, such as libraries and the headers needed to use them, and executables. It may also contain the sources necessary for building executables. A workspace loosely resembles the `rogue` tree of Rogue Wave's pre-SPM build model.