Build properties page
- Last Updated: March 12, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
The Build properties page consists of two tabs, Build and Source tab.
To access the Build and Source properties page, right-click an OpenEdge project name in the Project Explorer view and choose Properties from the context menu. Expand the Progress OpenEdge node in the tree view, and then click the Build node.
The Build properties page allows you to view and adjust options
related to compiling ABL source code and saving r-code.
The following controls are available on the Build tab:
| Project build destination |
The directory that will contain saved The OpenEdge compiler calculates the destination by appending the project relative path of the source to the path specified in the Build destination box. If, for example, the source file is in:
and you specify the build destination as:
the
When you compile a Note: The settings on the Source tab of
the PROPATH properties page override the build destination
specified here. Also note that the Source tab allows you to set
multiple source/destination folders. Whereas, the build
destination setting on the Build properties page only allows you
to specify a single destination folder for all the
.r files in the project. |
| Static file destination | The directory, relative to the project root folder, to which static files are copied. This setting is optional. |
| Generate Sonic invocation files on build | Automatically generate Sonic .esboe files whenever a build occurs
for the project. |
| Generate Rest invocation files | Automatically generate Data Service Catalog
.pidl files whenever a build
occurs for the project. For more information, see ABL Service artifacts. |
| Configure Workspace settings | Use this page to specify the file extensions associated with compilable ABL files. See also Editor Build options. |
| Compilable File Extensions | A comma separated list of the file type extensions that the OpenEdge Editor and SpeedScript can compile. |
The Source tab allows you to specify the directories in the project where source code resides, the environment (TTY or GUI) of the source code, and the build destination for r-code. You can specify multiple sets of source/destination folders.
The following fields and controls are available on the Source tab:
| Source directory viewer | Displays a list of folders in the selected
project that are designated as locations of source files under the
ROOT node. When you expand a directory in the list, you see four nodes: Environment (the runtime environment), Build Destination (where r-code is created), Excluded (lists the resources excluded from the build), and Platform node. You can specify a unique environment and build destination for each source directory in your project. Note: Source files that are not in one of the designated
source file folders shown in this view will still be built. The
destination folder for the r-code will be whatever is specified
as a build destination on the Build
properties page. If there is no build destination
specified, the r-code destination is the same folder that
contains the source file. |
| Add Folder | Displays a list of the folders in your project
that you can designate as containers of the project's source code.
It includes the root folder and any sub-folders that are resources
in your project structure. When you select a folder from the list, it appears in the Source directory viewer. |
| Remove | Allows you to remove the selected folder as a
container for source code. This does not remove the folder from the
file system, neither does it remove the folder as a project
resource. If Excluded node is selected, Remove allows deleting the excluded entries from this node so that they are included in the build. See also Include resources in the build. |
| Edit |
|
| Move Up | Changes the build order. You can move the resources or projects up to the top in the build process, so that they are built first. |
| Move Down | Changes the build order. You can move down the resources or projects to the bottom in the build process, so that they are built last. |
Related Links
- Set project properties
- Add Sonic ESB annotations
- Progress OpenEdge properties page
- AppBuilder properties page (Windows only)
- Assemblies properties page (Windows only)
- Configuration variables properties page
- Database connections properties page
- Modules properties page
- PROPATH properties page
- Configuration variables