Menu
▾
▴
[opengtoolkit-cvs] deab/user docs OGB Build File Dscr.htm,1.2,1.3
|
From: Konstantin S. <ks...@us...> - 2004-12-24 12:59:27
|
Update of /cvsroot/opengtoolkit/deab/user docs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23891/user docs Modified Files: OGB Build File Dscr.htm Log Message: Index: OGB Build File Dscr.htm =================================================================== RCS file: /cvsroot/opengtoolkit/deab/user docs/OGB Build File Dscr.htm,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** OGB Build File Dscr.htm 9 Dec 2004 04:13:36 -0000 1.2 --- OGB Build File Dscr.htm 24 Dec 2004 12:59:10 -0000 1.3 *************** *** 426,432 **** <p><b>keyname</b> = "VI path"</p> <p><i>[Top Level VIs]</i> section specifies VIs whose hierarchies are to be included in the build. Additionally, Top Level VIs will be set as "Top-Level" in destination LLBs if the its Destination is ! either an LLB or EXE. You can use any <i> keyname</i> for Top Level VIs; <i>keynames</i> for this section are arbitrary. ! A VI path may be either an absolute path, or a path relative to <i><a href="#General: Source Root">Source ! Root</a></i>.</p> <p><u>Example:</u></p> <p>[Top Level VIs]<br> --- 426,433 ---- <p><b>keyname</b> = "VI path"</p> <p><i>[Top Level VIs]</i> section specifies VIs whose hierarchies are to be included in the build. Additionally, Top Level VIs will be set as "Top-Level" in destination LLBs if the its Destination is ! either an LLB or EXE. You can use any <i> keyname</i> for Top Level VIs; <i>keynames</i> for this section are arbitrary.</p> ! <p>A VI path may be either an absolute path, or a path relative to <i><a href="#General: Source Root">Source ! Root</a></i>.<br> ! A VI path may contain wildcards in VI name to specify a group of VIs.</p> <p><u>Example:</u></p> <p>[Top Level VIs]<br> *************** *** 439,445 **** <p><b>keyname</b> = "VI path"</p> <p><i>[Dynamic VIs]</i> section specifies VIs whose hierarchies are to be included in the build. You can use any ! <i> keyname</i> for Dynamic VIs; <i>keynames</i> for this section are arbitrary. A VI path may be either an absolute path, or a path relative to <i><a href="#General: Source Root">Source ! Root</a></i>.</p> <p><u>Example:</u></p> <p>[Dynamic VIs]<br> --- 440,448 ---- <p><b>keyname</b> = "VI path"</p> <p><i>[Dynamic VIs]</i> section specifies VIs whose hierarchies are to be included in the build. You can use any ! <i> keyname</i> for Dynamic VIs; <i>keynames</i> for this section are arbitrary.</p> ! <p> A VI path may be either an absolute path, or a path relative to <i><a href="#General: Source Root">Source ! Root</a></i>.<br> ! A VI path may contain wildcards in VI name to specify a group of VIs.</p> <p><u>Example:</u></p> <p>[Dynamic VIs]<br> *************** *** 451,458 **** <p><b><a name="Exclude Lib Dirs"></a>[Exclude Lib Dirs from Build]</b></p> <p><b>keyname</b> = "dir/llb path"</p> ! <p><i>[Exclude Lib Dirs from Build]</i> section specifies directories and LLBs ! to exclude from build. All VIs, CTLs and non-VI resources like help files, ! shared libraries, etc. residing beneath the specified directories will not be ! included to a build. <i> Keynames</i> for this section are arbitrary. A path may be either an absolute path, or a path relative to <i><a href="#General: Source Root">Source Root</a></i>.</p> --- 454,461 ---- <p><b><a name="Exclude Lib Dirs"></a>[Exclude Lib Dirs from Build]</b></p> <p><b>keyname</b> = "dir/llb path"</p> ! <p><i>[Exclude Lib Dirs from Build]</i> section specifies directories, LLBs and ! individual files to exclude from build. Any VI, CTL or non-VI resource (such as runtime menu, shared library, help file, etc.) will not be included to the build if its path is either the same as or beneath any of ! the specified exclusion path. <i> Keynames</i> for this section are arbitrary.</p> ! <p>A path may be either an absolute path, or a path relative to <i><a href="#General: Source Root">Source Root</a></i>.</p> *************** *** 479,484 **** <i> Source Dir</i> of another Destination.</p> <p>A <i><b>Source Dir</b></i> may be either an absolute path, or a path relative to <i><a href="#General: Source Root">Source ! Root</a></i>. A <i>Source Dir</i> may be either a directory path or a path of ! LabVIEW library file (LLB).</p> <p>A <i><b>Target Dir</b></i> may be either an absolute path, or a path relative to <i><a href="#General: Build Root">Build Root</a></i>. A <i>Target Dir</i> may contain <u><KeepHierarchy></u> keyword as the last component of a path. In this case, a VI directory hierarchy in --- 482,486 ---- <i> Source Dir</i> of another Destination.</p> <p>A <i><b>Source Dir</b></i> may be either an absolute path, or a path relative to <i><a href="#General: Source Root">Source ! Root</a></i>. A <i>Source Dir</i> may be a directory path, a VI library (LLB) file path or even a VI/CTL/RTM path.</p> <p>A <i><b>Target Dir</b></i> may be either an absolute path, or a path relative to <i><a href="#General: Build Root">Build Root</a></i>. A <i>Target Dir</i> may contain <u><KeepHierarchy></u> keyword as the last component of a path. In this case, a VI directory hierarchy in *************** *** 493,498 **** is actually to be an executable file with EXE extension. This setting may be overridden by <u><KeepHierarchy></u> keyword.</p> ! <p>If the <i>Remove Diagrams</i> optional parameter is TRUE, all VIs in this Destination will have ! their diagrams removed, during the build.</p> <p>If <i><b>Default Destination</b></i> optional parameter is TRUE for a section, then that Destination will be used as the 'Default Destination'. The --- 495,500 ---- is actually to be an executable file with EXE extension. This setting may be overridden by <u><KeepHierarchy></u> keyword.</p> ! <p>If the <i><b>Remove Diagrams</b></i> optional parameter is TRUE, all VIs in this Destination will have ! their diagrams removed during the build.</p> <p>If <i><b>Default Destination</b></i> optional parameter is TRUE for a section, then that Destination will be used as the 'Default Destination'. The *************** *** 511,515 **** a password string to all VIs of the destination. If the parameter is missed or a value of it is an empty string, OGB uses a value of the <i><a href="#General: Apply New Password">Apply ! New Password</a> </i>parameter in [General] section as a default value. If a resulting password is an empty string, no password will be applied to VIs of the destination; otherwise, all the target VIs accept the password. A special case --- 513,517 ---- a password string to all VIs of the destination. If the parameter is missed or a value of it is an empty string, OGB uses a value of the <i><a href="#General: Apply New Password">Apply ! New Password</a> </i>parameter in <i> [General]</i> section as a default value. If a resulting password is an empty string, no password will be applied to VIs of the destination; otherwise, all the target VIs accept the password. A special case *************** *** 519,524 **** </p> <p><i><b>Namespace</b></i> is optional parameter that may be used to override a ! default <i><a href="#General: Namespace">Namespace</a></i>, specified in ! [General] section, for VIs of the destination. If the parameter is missed or a value of it is an empty string, OGB uses a default namespace. A special case is a use of <random:N> keyword to generate a random namespace and --- 521,526 ---- </p> <p><i><b>Namespace</b></i> is optional parameter that may be used to override a ! default <i><a href="#General: Namespace">Namespace</a></i>, specified in <i> ! [General]</i> section, for VIs of the destination. If the parameter is missed or a value of it is an empty string, OGB uses a default namespace. A special case is a use of <random:N> keyword to generate a random namespace and |
