From a command line
When you deploy or build a workspace 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 and
workspaces.
|
Option |
Description |
|---|---|
|
/workspace workspacepath |
Open the workspace workspacepath |
|
/target targetpath |
Open the target targetpath |
|
/deploy |
Deploy the workspace and exit |
|
/fullbuild |
Fully build the workspace and exit |
|
/incrementalbuild |
Incrementally build the workspace and |
|
/output outputpath |
Log the contents of the Output window to |
As with other command-line options, you need only 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 option. You need to create
projects and specify build and deploy options for the workspace 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: mpcdshop.out, and
exits PowerBuilder:
|
1 |
pb190 /w D:CDShopCDShop.pbw /d /out D: mpcdshop.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.