Add/Edit a build rule

Figure 1. Add/Edit Build Rule dialog

Label

Enter a label to be assigned to the rule.

File type

Defines the MIME-type of the source files that can be compiled with this Build rule; click the icon on the right to display the File Type Selection dialog. Select the file type from a list generated from the File Associations in Genero Studio Preferences. Use the Search field to limit the display of the list; enter the file extension, or the words Genero or studio, for example, to display only the corresponding file types. The icons can be used to display the list by category, and to expand or contract a category.

Output files

Enter the list of files that are generated by the Build rule. All the predefined file node variables can be used when specifying the path of the file.

Intermediate files

Indicates which files are generated during compilation, as intermediate files, before generating the output file. This displays the Intermediate files in the Project view.

Additional dependencies

The additional dependencies is a list of files used to verify that the build is up to date. If one of these files has a modified date more recent than any of the output files, the build is considered not up to date and the build rule will be executed.

Example

For a preprocessor named mypp for source files (*.my), the Build Rule for the mime type "text/my" would be:

mypp $(InputPath) -o $(TargetDir)/$(InputBaseName).4gl 
$(fglcomp) $(TargetDir)/$(InputBaseName).4gl
$(delete) $(TargetDir)/$(InputBaseName).4gl

Redirect output

When a command is executed in a build, link, execution rule or in a user action, the output (standard or error) is displayed in the Output view. You can redirect the output to a file. For example, if you write echo "Hello World" in a build rule, Hello World is displayed in the Output view. To redirect the output to a file, use standard Linux™ syntax such as: echo "Hello World" > "c:\file.txt". Supported syntax is >, 1>, >>, 2>, 1>&2, 2>&1.