To deploy projects using the PBC approach, you can execute the PBAutoBuild250.exe file with the /pbc, /d and related parameters. (Note that you can deploy the PowerBuilder C/S Application projects only.)
PBAutoBuild250 /pbc /d filename [/compilemode] [/options]
/pbc and /d parameters are required and must be used together; the other parameters are optional.
For example,
PBAutoBuild250 /pbc /d "test11.pbt" /o "test11.exe" /r "test11.pbr" /w n /f /m y /tr n /in n /op 0 /x 32 /bg y /p "PowerBuilder Enterprise Series" /cp "Appeon" /de "Appeon Product File" /cr "Contains licensed copyright material by Appeon" /v "1.0.0.1" /fv "1.0.0.1" /ge 1 /le 0 /ps n
| Parameters | Required | Description |
|---|---|---|
|
/pbc |
Yes |
Deploys the project with the PBC approach. The /pbc parameter (PBC approach) must be used together with the /d and related parameters. |
|
/d |
Yes |
Name of the workspace, solution, target, or project file to be deployed to EXE and DLL/PBD files. It supports the following file types: .pbw, .pbsln, .pbt, and .pbproj (.pbl is not supported currently). For example, PBAutoBuild250 /pbc /d test11.pbw All the other related files will be deployed to the same folder as the EXE file specified in the /o parameter. PowerBuilder IDE -> Project Painter: Executable file name option |
|
/f |
No |
Full compilation mode. When not specified, full compilation mode is used by default. |
|
/i |
No |
Incremental compilation mode. |
|
/o |
No |
Name of the application executable file to be created. All the other related files will be deployed to the same folder as the EXE file. For example: /o d:\fo\test11.exe. If not specified, the same name as the target (.pbt) or project (.pbproj) file will be used. PowerBuilder IDE -> Project Painter: Executable file name option |
|
/r |
No |
Name of a PBR (PowerBuilder resource file) that will be used to build the executable file. For example, /r test11.pbr. PowerBuilder IDE -> Project Painter: Resource file name option Note that only one general resource file can be specified in this parameter (unlike PowerBuilder IDE which can specify a separate resource file for each PBL file). |
|
/x |
No |
Whether the platform to run the EXE file is 32-bit or 64-bit. Values can be 32 (the default) or 64. For example, /x 32. 32-bit EXE file can only run with the 32-bit runtime files, and 64-bit EXE file can only run with the 64-bit runtime files. PowerBuilder IDE -> Project Painter: Platform option |
|
/cp |
No |
Name of the company. Default is empty. If there’s space in the company name, the name should be quoted, for example, /cp "Appeon SZ". PowerBuilder IDE -> Project Painter: Company name option |
|
/p |
No |
Name of the product. Default value is “PowerBuilder Enterprise Series”. If there’s space in the product name, the name should be quoted, for example, /p "PowerBuilder Enterprise Series". PowerBuilder IDE -> Project Painter: Product name option |
|
/de |
No |
Description of the product. Default is empty. If there’s space in the description, the description should be quoted, for example, /de "Appeon Product File". PowerBuilder IDE -> Project Painter: Description option |
|
/cr |
No |
Copyright statement of the product. Default is empty. If there is space in the copyright description, the description should be quoted, for example, /cr "All rights reserved.". PowerBuilder IDE -> Project Painter: Copyright option |
|
/v |
No |
Version of the software. Default value is “1.0.0.1”. PowerBuilder IDE -> Project Painter: Product version option (Properties displayed for executable) |
|
/fv |
No |
Version of the file. Default value is “1.0.0.1”. PowerBuilder IDE -> Project Painter: File version option (Properties displayed for executable) |
|
/vn |
No |
Version of the software which consist of four integer values representing the major version number, minor version number, fix version number, and build number, with each value separated by a decimal point, for example "11.0.0.3012". PowerBuilder IDE -> Project Painter: Product version option (Executable version used by installer) |
|
/fvn |
No |
Version of the file which consists of four integer values representing the major version number, minor version number, fix version number, and build number, with each value separated by a decimal point, for example "11.0.0.3012". PowerBuilder IDE -> Project Painter: File version option (Executable version used by installer) |
|
/w |
No |
Whether to use the Windows classic style. Values are:
PowerBuilder IDE -> Project Painter: Windows classic style option |
|
/m |
No |
Whether to generate machine code executables and dynamic libraries. Values are:
PowerBuilder IDE -> Project Painter: Pcode option and Machine code option |
|
/tr |
No |
Whether to generate a trace file for troubleshooting or profiling your application when you run the executable file. Values are y and n (the default). This parameter takes effect only when machine code executable is generated. PowerBuilder IDE -> Project Painter: Trace information option |
|
/in |
No |
Whether to display context information (such as object, event, and script line number) for runtime errors. Values are y and n (the default). This parameter takes effect only when machine code executable is generated. PowerBuilder IDE -> Project Painter: Error context information option |
|
/op |
No |
Optimization level. Values are:
This parameter takes effect only when machine code executable is generated. PowerBuilder IDE -> Project Painter: Optimization option |
|
/bg |
No |
Whether to enable any code that you placed in DEBUG symbol conditional compilation code blocks. Values are y (the default) and n. PowerBuilder IDE -> Project Painter: Enable DEBUG symbol option |
|
/ge |
No |
Whether to generate manifest. Values are:
PowerBuilder IDE -> Project Painter: Generation options option |
|
/le |
No |
Execution level of manifest. This parameter takes effect only when /ge is set to 1 or 2. Values are:
PowerBuilder IDE -> Project Painter: Execution level option |
|
/ps |
No |
Whether to allow access to the protected system UI. Values are y and n (the default). This parameter takes effect only when /ge is set to 1 or 2. PowerBuilder IDE -> Project Painter: Allow access to protected system UI option |
|
/pd |
No |
Whether to generate the PBD/DLL file for a PBL. Values are:
PowerBuilder IDE -> Project Painter: PBD option When there are more than one PBLs in an application, each PBL can have its own /pd value. For example, when there are three PBLs, /pd nnn indicates only EXE file is generated and no PBD/DLL file is generated; /pd yny indicates the first and the third PBLs will have PBD/DLL files generated; /pd n indicates the first PBL will not have PBD/DLL file generated, and the second and the third PBL will have PBD/DLL files generated because the default value is y. If you specify to generate the EXE file only without the PBD/DLL file, make sure to test that the EXE file can run correctly. |
|
/rt |
No |
The version of PowerBuilder Runtime that will be used to compile the application executable, for example, /rt 25.0.0.1234. If this parameter is not set, then the runtime version configured in the PowerBuilder IDE will be used; and if no PowerBuilder IDE is installed on the current machine, then the latest runtime within the same major version as PowerBuilder Compiler will be used. |
