When you build an application from a Business Application diagram, the build rules define the various files that are input into the Code Generation Engine and the application code files that are output.
Figure 1. Code Generation flow
The build rules define the series of commands used to build and generate the code. View default build rules selecting
. This example shows the build rules used to generate the code for a Program entity in the Business Application diagram.Figure 2. Default build rule for a generated program entity
Build rule command | Description |
---|---|
$(generate) | The $(generate) command creates an intermediary XML file from the schema, Business Application diagram, and Form. |
$(blockpoint) -code | BLOCK/POINT is extracted from previously generated and modified code. |
tclsh | The tclsh executable generates the final file by using both a Tcl template file and the intermediary XML file crated by the $(generate) command. |
$(blockpoint) –storeGenerated | Extracted BLOCK/POINT code is put back into the generated code. |
$(fglcomp) | The fglcomp tool compiles BDL program sources files into a p-code version. |
$(move) | Moves the given file or directory to the given destination in a platform independent way. |
To better understand what is happening during the build of the program, turn on verbose mode using Compile a diagram file, program, or application and view the results in the output. .