When you deploy or build a workspace/solution from a command line, PowerBuilder starts, completes the build, and exits as soon as the operation is completed. To retain a log file for the session, you can send the contents of the Output window to a file. The following table shows command-line options for building and deploying targets/projects and workspaces/solutions.
|
Option |
Description |
|---|---|
|
/workspace workspacepath or solutionpath |
Open the workspace workspacepath or solution solutionpath |
|
/target targetpath or projectpath |
Open the target targetpath or project projectpath |
|
/deploy |
Deploy the workspace/solution and exit |
|
/fullbuild |
Fully build the workspace/solution and exit |
|
/incrementalbuild |
Incrementally build the workspace/solution and exit |
|
/output outputpath |
Log the contents of the Output window to outputpath |
As with other command-line options, you need only to use the initial letter or letters of the option name as long as the option is uniquely identified. The deploy, fullbuild, and incrementalbuild options can be used only with the workspace/solution option. You need to create projects and specify build and deploy options for the workspace/solution in PowerBuilder before you start a build from the command line. Deploy builds the projects in the target in the order listed on the Deploy page of the target's properties dialog box.
Example
This example assumes that the location of the PowerBuilder executable file is in your system path. It opens the workspace called CDShop, builds and deploys the targets in the workspace according to your specifications in the workspace and target properties, records the content of the Output window in the file D:\tmp\cdshop.out, and exits PowerBuilder:
pb250 /w D:\CDShop\CDShop.pbw /d /out D:\tmp\cdshop.out
The output from all the tab pages in the Output window and from all the projects is included in the output file.
There are additional command-line options you can use to start PowerBuilder. See Using command line arguments.
