Maximizing Your Results with SoftBench
Understanding Projects
Project file set | The source, documentation and test files you wish to |
| associate with the project. |
Project targets | The executables, libraries, message catalogs, and other |
| files that are the product of one or more builds. |
Build Configurations Instructions for how to transform your source files into your target files.
Project names contain regular characters. Control characters, spaces, and punctuation characters special to the shell are not allowed in project names. The files and targets that comprise your project are located under your local workspace root. SoftBench's project description data contains lists of these files and their relationships.
When you change file and target information in SoftBench, you change only SoftBench internal descriptions of their relationships. For example, deleting a file from a project only changes your project description data. It has no impact on your files in the file system.
Subprojects are projects with a defined dependent relationship to a parent project. A subproject relationship implies a build order dependency. A project is always an entity to itself; that is, it does not dynamically inherit options or build information from any other project. Examples of subprojects include:
•a project to build a library that is linked into a parent project target
•a project to build an executable that is used to generate files or targets in the parent project
Building TargetsSource files are files you create and edit directly. A target is a project file that is the end product of a build. Examples of targets include linked executables, shared libraries, archive libraries, and message catalogs.
22 | Chapter 1 |