02.05.2013 Views

User Guide - MKS

User Guide - MKS

User Guide - MKS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Window Type Opened Associated Environment Variable<br />

Project For an open project window:<br />

Source Integrity Graphical <strong>User</strong> Interface<br />

<strong>MKS</strong>SI_WINDOW=project<br />

<strong>MKS</strong>SI_FILE=server-side-project-path<br />

<strong>MKS</strong>SI_NMEMBER=number of <strong>MKS</strong>SI_MEMBERxx entries<br />

<strong>MKS</strong>SI_NSUBPROJECT=number of <strong>MKS</strong>SI_SUBPROJECTyy entries<br />

If any members are selected, then the following variables apply:<br />

<strong>MKS</strong>SI_MEMBERxx=path-relative-to-project<br />

<strong>MKS</strong>SI_MEMBER_PROJECTxx=server-side-project/subproject-path<br />

If any subprojects are selected, then the following variables apply:<br />

<strong>MKS</strong>SI_SUBPROJECTyy=path-relative-to-project<br />

<strong>MKS</strong>SI_SUBPROJECT_PROJECTyy=server-side-project/subprojectpath<br />

That is, if there are n members selected and m subprojects selected then you have<br />

n occurrences of <strong>MKS</strong>SI_MEMBER numbered from 1 to n and the number n is also<br />

passed in <strong>MKS</strong>SI_NMEMBER. There are also occurrences of <strong>MKS</strong>SI_SUBPROJECT,<br />

numbered from 1 to m, and the number m is passed in <strong>MKS</strong>SI_NSUBPROJECT.<br />

If a subdirectory is selected, then it is as if that subdirectory is recursively<br />

expanded (only the directories, not subprojects) and all members are selected.<br />

Because a given member may not be in the top level project that is open in the<br />

view, each variable for <strong>MKS</strong>SI_MEMBER and <strong>MKS</strong>S_SUBPROJECT has a<br />

corresponding entry for <strong>MKS</strong>SI_MEMBER_PROJECTxx and<br />

<strong>MKS</strong>SI_SUBPROJECT_PROJECTxx. Therefore, each MEMBER/SUBPROJECT<br />

variable is relative to its corresponding PROJECT entry, not to the top level<br />

indicated in <strong>MKS</strong>SI_FILE.<br />

For example:<br />

i=1<br />

while [ $i -le $<strong>MKS</strong>SI_NMEMBER ]<br />

do<br />

eval si command<br />

-P\${<strong>MKS</strong>SI_MEMBER_PROJECT$i}\${<strong>MKS</strong>SI_MEMBER$i}<br />

let i=i+1<br />

done<br />

Note: If set, the environment variables <strong>MKS</strong>SI_VARIANT and <strong>MKS</strong>SI_BUILD are<br />

also exported when invoking an si command with the options for --devpath and<br />

--projectrevision.<br />

Sandbox For an open sandbox window:<br />

<strong>MKS</strong>SI_WINDOW=sandbox<br />

<strong>MKS</strong>SI_FILE=full-path-to-sandbox<br />

<strong>MKS</strong>SI_NMEMBER=number of <strong>MKS</strong>SI_MEMBER objects<br />

<strong>MKS</strong>SI_NSUBPROJECT=number of <strong>MKS</strong>SI_SUBPROJECT objects<br />

Note: The variables <strong>MKS</strong>SI_MEMBERxx= and <strong>MKS</strong>SI_SUBPROJECTxx= take the<br />

same settings as for a project window. The corresponding variables<br />

<strong>MKS</strong>SI_MEMBER_SANDBOXxx and <strong>MKS</strong>SI_SUBPROJECT_SANDBOXxx are also as<br />

described for a project. If applicable, <strong>MKS</strong>SI_VARIANT and <strong>MKS</strong>SI_BUILD are<br />

also set.<br />

87

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

Saved successfully!

Ooh no, something went wrong!