a build, or during an "Analyze File Set" operation.
Subproject A subproject is a project with a defined build dependency relationship to a parent project. Examples of subprojects include:
•a project to build a library that will be linked into a parent project executable
•a project to build an executable used to generate files or targets in the parent project
Subprojects are projects in their own right, and do not inherit options or build instructions from the parent project (except at creation time if they are created through the "File: Convert to Project…" process). A subproject relationship does not imply "inclusion"; that is, the file set of the subproject is not a subset of the parent project file set.
Symbolic Name A special name or code for a file that associates it with a certain release. If subsequent revisions of this file form a branch, the symbolic name applies to the entire branch. Also known as usename or tag.
Synchronous Mode The program interacts with the X Window System in such a way that events are not buffered, but are written/read as they happen.
Target A project file that is the end product of a build; for example, a linked executable, shared library, archive library, or message catalog.
Targets share the following characteristics:
•A target belongs to only one project. You can, however, use the same target name in more than one project.
•SoftBench builds targets in no specific order unless you create a build order dependency between targets.
•You can (and usually do) define targets before they exist on the file system.
•Targets have a physical file system location, usually the local workspace root, which can be changed by modifying the target's properties.
•Project build targets have an associated build configuration which provides build rules and tool interactions.
•Project build targets have
386