Target Overview Attributes

OpenMake Meister for Intelligent Builds / Creating and Managing Targets

Target Overview Attributes

When you first open a Target in the Target Editor, you will see the Overview tab. The Overview tab contains the basic information about the Targets to be built: the Project that your Target belongs to, the file name of your Final Target, location to build the Intermediate and Final Targets, the Build Service to be used, and the Operating System. The following is a list of the Target Overview Attributes and their descriptions.

Table PB-3 Target Overview Attributes

Attribute	Description
OS	An operating system is automatically displayed after you select a Build Service for building the Final Target. If the Final Target is defined on multiple Operating Systems, separate Final Targets must be defined for each Operating System.
Build Service	A Build Service defines how the Target is to be built. Build Services are generic and do not contain specific names of source files or libraries.
Project	This field determines the Project to which the Target will be associated. The Target Project is a required field.
Target Name	The Final Target Name is the name of the binary that you are building. Your Final Target name extension must correspond with the final object extension as defined in the associated Build Service, for example an .exe for a “C” language Build Service or a Jar for a Java Jar Build Service. The Final Target Name is a required field.
Target Directory	By default, built Final Targets are placed in the Build Directory, which is either the Workflow Build Directory if running a Workflow or the current working directory if running the build from a command line process. It is often desirable, however, to place Final Targets in unique directories to prepare them for distribution. From the Target Overview screen there are two ways to define a Final Target directory: • Fill in the Final Target field with the name of the directory, for example, bin. • Append the desired directory name to the Final Target name, for example bin\hello.exe. In both cases the Final Target hello.exe will be built in the “bin” directory under the Build Directory. The Final Target Directory is not a required field.
Intermediate Directory	It is often useful to save all Intermediate Targets separated from Final Targets in a unique directory under the Build Directory. An intermediate Target is an .obj or a .class file. If Intermediate Files are built, as per the Build Rules of the Final Target’s Build Service, then the Intermediate Directory field will be editable. If the selected Build Service does not support creation of Intermediate Targets then this field will not be available. If Intermediate Targets are part of the build but no name is given to an Intermediate Directory, the Final Directory will also act as the Intermediate Directory. If no Final Directory is defined, then all Intermediate Targets will be built in the Build Directory. The Intermediate Directory is not a required field.