Build properties page

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:

Build only when source files are newer than r-code	Compile only those source files for which no up-to-date .r files are present. This option can save time when compiled code already exists.
Project build destination	The directory that will contain saved .r files. If this field is blank, .r files are saved in the same directory as the source files. 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: C:\workspace\myproject\src\subdir1 and you specify the build destination as: C:\workspace\rcode the .r files end up in: C:\workspace\rcode\src\subdir1 When you compile a .cls file, the directory structure below the path specified in the Build destination box matches the internal package name declared in the .cls file. 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 BPM invocation files	Automatically generate BPM .bizoe files whenever a build occurs for the project. Generated .bizoe files are stored in the location specified in the File Destinations properties page.
Generate Rest invocation files	Automatically generate Data Service Catalog .json files whenever a build occurs for the project. For more information, see Data Object 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. For projects prior to 11.0, by default a ROOT node is added on importing the project. In releases prior to 11.0, the Source tab contained no entries by default. See also opening older version project with Progress Developer Studio for OpenEdge 11.0. 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 including resources in the build.
Edit	If a source directory is selected, Edit allows you to change to a different source folder in the project. If Environment is selected, Edit allows you to designate the runtime environment (GUI or TTY) of your code. By default, the environment is all, which signifies that your code is intended to run in both environments. If Build Destination is selected, Edit allows you to designate where to put the r-code in the file system. If Excluded node is selected, Edit allows you to modify the excluded entries (exclude or include in the build).
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.