PowerBuilder Compiler (PBC) is integrated into PBAutoBuild and the PBC executable file (pbc250.exe) is no longer provided in PowerBuilder 2025.
The parameters supported by PBC will be kept unchanged and supported in exactly the same way as before by PBAutoBuild. You only need to add /pbc parameter to the PBAutoBuild command (to switch to the PBC approach).
That is to say, you need to replace "pbc220" or "pbc250" with "pbautobuild250 /pbc" and leave the other parameters unchanged. For example,
-
To compile a project using PBC:
You need to modify the following command:
pbc250 /c pbwfile or pbtfile [/compilemode]
To this command:
pbautobuild250 /pbc /c pbwfile or pbtfile [/compilemode] //include /pbc to switch to the PBC approach, the other parameters remain unchanged
-
To deploy a project using PBC:
You need to modify the following command:
pbc250 /d pbwfile or pbtfile [/compilemode] [/options]
To this command:
pbautobuild250 /pbc /d pbwfile or pbtfile [/compilemode] [/options] //include /pbc to switch to the PBC approach, the other parameters remain unchanged
After integrating PBC into PBAutoBuild, you must include the /pbc parameter if you want to build the project using the PBC approach, otherwise (if /pbc is not specified), the project will be built with the PBAutoBuild approach (the default mode).
For detailed information, refer to the section called “PBAutoBuild supported parameters” in Users Guide.
For PowerServer/PowerClient projects, PBAutoBuild supports deploying the project only, allowing you to skip the compilation process.
If the project has been compiled before, you can use the /deploy parameter to bypass compilation.
For example,
PBAutoBuild250 /f c:\SalesDemo_cloud.json /deployIf SalesDemo_cloud.json contains configurations for multiple projects, then every project will be deployed only (without being compiled or built again).
