Ultra-fast compiler

PowerBuilder 2025 introduces a completely new ultra-fast compiler, in addition to the standard PBL compiler. The ultra-fast compiler processes code stored as plain text in the new solution format and offers the following benefits:

  • 2-3x faster builds. Compared to the standard compiler, the ultra-fast compiler can significantly reduce compilation time by leveraging the Abstract Syntax Tree (AST), multi-threading, and concurrent processing. Full builds are at least 2-3 times faster and incremental builds are even faster.

    Note

    For faster builds in the solution format, use "PowerScript Build" instead of "Full Build", to speed up the process by skipping DataWindow recompilation. A "PowerScript Build" refers to a build process that skips recompiling DataWindows which can be time-consuming if they have not changed. This can be useful for optimizing build time, especially when DataWindows have not been modified.

    You can right click the solution or project in the system tree, and then select "PowerScript Build" from the popup menu.

  • Eliminates code corruption. Source code storage is now separate from the P-code, preventing unexpected compilation errors or system malfunctions from corrupting the source code.

  • Automatic project conversion. Projects in the workspace format that utilize the standard PBL compiler can be automatically converted to the new solution format that utilizes the ultra-fast compiler.

  • CI/CD integration. Support for CI/CD workflows is now built-in.

Table below compares the key features of the ultra-fast compiler and standard compiler.

 

Ultra-Fast Compiler

Standard Compiler

Source code compiled

Source code in plain text format, with one object in one text file

Source code in binary format, with multiple objects in one PBL file

Pcode and Machine code

Supports Pcode only

Note: Machine code is unsupported, meaning you cannot build Dynamic Link Libraries (DLL files). If the application project is set to generate machine code, it will be automatically switched to Pcode when the application is converted to the solution format.

Supports Pcode and Machine code

Multi-thread or single-thread

Supports multi-thread and multi-process.

Note: The compiler and the IDE run in separate threads.

Supports single-thread and single-process.

The compiler runs in the same thread as the IDE.


We conduct performance comparison tests for incremental build, full build, and deployment in the workspace format and solution format, as shown in the table below. The larger the application, the more significant the performance improvement.

App size

Full Build

Incremental Build

(32-bit, Pcode)

(Modified only app object and one window in another PBL)

Full Deployment

(32-bit, Pcode)

Workspace

Solution

Workspace

Solution

Workspace

Solution

58 PBLs, 370 MB in size

816

112

771

115

1055

168

(unit: seconds)