Menu
▾
▴
[opengtoolkit-cvs] deab/developer docs DEAB File Dscr.htm,1.2,1.3
|
From: Konstantin S. <ks...@us...> - 2004-11-01 12:54:53
|
Update of /cvsroot/opengtoolkit/deab/developer docs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13449/developer docs Modified Files: DEAB File Dscr.htm Log Message: Index: DEAB File Dscr.htm =================================================================== RCS file: /cvsroot/opengtoolkit/deab/developer docs/DEAB File Dscr.htm,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** DEAB File Dscr.htm 30 Oct 2004 21:31:11 -0000 1.2 --- DEAB File Dscr.htm 1 Nov 2004 12:54:02 -0000 1.3 *************** *** 214,218 **** <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 keyname for Top Level VIs. Keynames 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> --- 214,218 ---- <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> *************** *** 225,229 **** <p><b><a name="Dynamic VIs"></a>[Dynamic VIs]</b></p> <p><b>keyname</b> = "VI path"</p> ! <p><i>[Dynamic VIs]</i> section specifies VIs whose hierarchies are to be included in the build. Keynames 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> --- 225,230 ---- <p><b><a name="Dynamic VIs"></a>[Dynamic VIs]</b></p> <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> *************** *** 238,242 **** 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. Keynames 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> --- 239,243 ---- 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> |
