![]() |
OpenMake Meister |
Targets can be created and edited through the Target Editor available through the Target Explorer found under the OM Meister Perspective. In addition, Targets can be automatically generated via an IDE. Adding Targets to your Project is simplified by the use of Build Services. The Build Service defines a “blueprint” for defining the Target, and it is graphically displayed in the Target Detail tab. Table PB-1 will get you started with creating your Targets through the Target Editor Wizard.
Table PB-1 Adding a Target to Your Project
Step |
Action |
1 |
Go to the Target Explorer tab found under the OM Meister Perspective. |
2 |
Right Click in the left pane of the Target Explorer and Select New – Target to launch the Target Wizard. |
3 |
Select the Build Service to be used by your Target. Build Services are organized by Operating System. For example, if you are building a Java Jar, select the Java Operating System and select the Java Jar Build Service. Select Next. |
4 |
Enter the Name of your Target. It is recommended to use a name that refers to the Final Target being built, for example foo.jar or foo.exe. Keeping the names of the Final Target and Target Definition file similar makes it easy to determine to which Final Target the Target Definition File belongs. Select Finish. |
5 |
You will now be brought to the Target Overview Screen. Enter the Project which the Target is to be associated. |
6 |
Select the Detail tab at the bottom of your screen to enter your Target's file dependencies. You do not need to reference high level directory names. This is done by the Project's Dependency Directories at build time. Additionally, you do not need to add any low level dependency information. Dependency Discovery will expose any nested files such as .h files included in .c files, or .java files referenced inside other java files. |
7 |
Select the Add Deps Button and enter the file name associated to each step required to build your Target. For example, for a Java Jar Target, the Set Classpath step should have the rt.jar added. Similarly, for creating a C executable, the compile step would have the .c source files listed. |
8 |
You can also use the Import Deps Button to select multiple files from the file system or use a directory name with wildcards for referring to all files in a directory. |
9 |
Define any compile flags that may be unique to your Target. The Build Service already defines Standard Options displayed in the Standard Options field; however you’re Target may use Custom Options. Enter the Custom Options using the Custom Options field. |
Note: When working with Microsoft Tools, the project file is the only Dependency that needs to be added. The project file will be scanned for all Target Source Code and Library information. This feature is available for the following .Net project and solution level files (.vbproj, .sln. .csproj, .vcproj, .vdproj) Visual Studio project files (.vbp, .dsp) .
Any post-build commands in the .NET projects or solutions will NOT be executed. Post-build commands are often dependent on the machine and the user. By separating the post-commands from the build, the build can be executed on different machines in an identical way.