Workbench User Guide > Workbench User Guide > Managing and Deploying Applications > How You Can Compile Applications and Components > Compile an Application
Was this helpful?
Compile an Application
The CompileApp utility compiles an application or any of its components. Compilation is done automatically when you make an image, but you can also compile explicitly as a separate step. If there are any compilation errors, the utility displays an error message and continues compiling the next component.
The easiest way to compile an application is to access the CompileApp utility from the Develop tab.
To use the CompileApp utility
1. Select the application you want to compile in the Applications portlet of the Develop tab.
2. Click Project, Compile.
The Compile dialog appears.
3. Set parameters for the specified application.
See the descriptions for each of these parameters in Parameters for the CompileApp Utility.
4. Click Go.
Parameters for the CompileApp Utility
You can specify the following parameters using the Compile dialog:
Ignore Locks (-l)
Unlocks any locked components
OpenSQL Warnings (-wopen)
Produces a warning error at compilation time for any SQL statement that is not compliant with OpenSQL
Force Compilation (-f)
Forces recompilation of all application components, even those that have not been changed since the last compilation.
If you are compiling a single component (with the -ccomponent parameter), this parameter forces compilation of the specified component.
Display Errors (-e)
Causes OpenROAD to write the component's 4GL script and any errors to the Trace window, if any component has compilation errors
Treat Warnings as Errors (-w)
Instructs OpenROAD to treat compiler warnings as errors.
Username (-u)
Lets you use this command as if you were another user, username.
• You, not username, own all files created by OpenROAD.
• This entry field can be used only if Execute in Background is enabled.
Log Path (-L)
Specifies the name of a log file. This entry field can be used only if Execute in Background is enabled and Trace Window is set to Yes. If the log path specified is not a full path, the file is created in the ingres\files directory.
Note:  This parameter is only available when accessing this utility from the Project menu.
Trace Window (-T)
Lets you control display of the Trace window by entering one of the following values:
All
Specifies that the Trace window does appear
Yes
Specifies that the Trace window appears but suppresses informational messages output by the system
Yes (Minimized)
Specifies that the Trace window appears minimized as an icon
No
Specifies that the Trace window does not appear, and a log file is not created
Note:  This entry field can be used only if Execute in Background is enabled.
Append to Log File (-A)
Appends the trace output of the current command to the end of the existing error log file. Otherwise, that log file is replaced. This entry field can be used only if Execute in Background is enabled.
Note:  The error log file, w4gl.log, is located in %USERPROFILE%\AppData\Local\OpenROAD\Profiles\installation_ID. If the -L flag is passed, a new name and location can be provided for the OpenROAD log file.
Execute in Background
Begins a new process while you are using this utility.
If enabled, Execute in Background makes Username, Log Path, Trace Window, and Append to Log File available for use.
Note:  This parameter is only available when accessing this utility from the Project menu.
Note:  You can set defaults for this utility using the Set Tool Defaults dialog. see Set Defaults.
Last modified date: 12/20/2023