02.05.2013 Views

Description - Mks.com

Description - Mks.com

Description - Mks.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

development path name.<br />

--type=build configures the subproject as a static subproject based upon a specific revision of the master<br />

project that is used for building or testing the project, but not for further development. This option is used with -<br />

r subproject revision or --subprojectRevision=subproject revision.<br />

--type=default configures the subproject based on the type that is consistent with the parent project that<br />

you are adding the subproject to. For example, if you add a subproject to a normal project, the subproject is<br />

added as a normal type. For information on what the default type is, see your administrator.<br />

-P project name<br />

--project=project name<br />

specifies the path and name of the project you want to add the shared subproject to, for example,<br />

c:/Aurora_Program/bin/project.pj.<br />

subproject location<br />

specifies where in the project you want the shared subproject to appear, for example,<br />

c:/Aurora_Program/bin/Libra/.<br />

DIAGNOSTICS<br />

See the diagnostics reference page for possible exit status values.<br />

PREFERENCES<br />

Using si setprefs or si viewprefs, you are able to set or view the preference keys for this <strong>com</strong>mand.<br />

SEE ALSO<br />

Commands:<br />

si addsubproject, si checkpoint, si configuresubproject, si createproject, si<br />

createsandbox, si createsubproject, si drop, si dropproject, si importproject, si<br />

projectinfo, si projects, si viewproject<br />

Miscellaneous:<br />

ACL, diagnostics, options, preferences<br />

242 of 457

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!