User Guide - MKS

Chapter 5: Project and Sandbox Operations
128
3 Under Options, select the configuration type you want for the
subproject. The available types are:
Normal configures a subproject based upon the current state of the
subproject.
Variant configures a subproject based upon a specific revision of
the master project and is used for branching off the main
development path.
NOTE
From the Development Path Name list, select a development path
name, for example, Aurora_Beta_Variant.
The Variant option is unavailable if there are no available development paths.
To create a development path, see “Creating a Development Path” on page 141.
Build configures a static subproject based upon a specific revision
of the master project that is used for building or testing the
project, but not for further development.
To specify a revision to base the build project, do one of the
following:
Select Revision, and from the list select a project revision
number, for example, 1.1.
Select Label, and from the list select a project label.
Reset to default value configures a subproject to the parent project
type.
4 Click OK to complete the operation.
The subproject is re-configured.
Subprojects configured as a build subproject appear with a build
project icon (Project window: or Sandbox window: ), and the
revision or label that the build project is based on, for example,
tools.pj (1.1).
Subprojects configured as a variant subproject appear with a variant
project icon (Project window: or Sandbox window: ), and the
u s e r g u i d e