Menu
▾
▴
[opengtoolkit-cvs] deab/developer docs DEAB File Dscr.htm,1.9,1.10 DEAB Glossary.htm,1.6,1.7 DEAB Overview.htm,1.3,1.4 DEAB Pathroots Dscr.htm,1.1,1.2 DEAB Revision File Dscr.htm,1.1,1.2
|
From: Konstantin S. <ks...@us...> - 2004-11-09 10:13:32
|
Update of /cvsroot/opengtoolkit/deab/developer docs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28390/developer docs Modified Files: DEAB File Dscr.htm DEAB Glossary.htm DEAB Overview.htm DEAB Pathroots Dscr.htm DEAB Revision File Dscr.htm Log Message: Index: DEAB Pathroots Dscr.htm =================================================================== RCS file: /cvsroot/opengtoolkit/deab/developer docs/DEAB Pathroots Dscr.htm,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** DEAB Pathroots Dscr.htm 30 Oct 2004 19:00:28 -0000 1.1 --- DEAB Pathroots Dscr.htm 9 Nov 2004 10:12:20 -0000 1.2 *************** *** 4,18 **** <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> ! <title>Untitled Document</title> </head> ! <body> <b>Pathroots</b> - The following Pathroots may be used, such that a path is specified relative to the pathroot. For example: <br> <br> ! <font face="courier"><a href="Exclude Lib Dirs from Build">Exclude Lib Dirs from Build</a> </font><br> <font face="courier">Exluded Dir 1 = <user.lib>/_OpenG </font><br> ! <font face="courier">Exluded Dir 2 = <vi.lib> </font><br> ! <br> ! <table border="1"> <tbody> <tr> --- 4,18 ---- <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> ! <title>DEAB Pathroots</title> </head> ! <body style="font-family: Verdana; font-size: 10pt"> <b>Pathroots</b> - The following Pathroots may be used, such that a path is specified relative to the pathroot. For example: <br> <br> ! [<font face="courier"><a href="Exclude Lib Dirs from Build">Exclude Lib Dirs from Build</a>] </font><br> <font face="courier">Exluded Dir 1 = <user.lib>/_OpenG </font><br> ! <font face="courier">Exluded Dir 2 = <vi.lib> </font> ! <p> </p> ! <table border="1" style="font-family: Verdana; font-size: 10pt" cellspacing="0"> <tbody> <tr> *************** *** 36,84 **** </tr> <tr> ! <td><application> </td> <td> C:\Program Files\National Instruments\LabVIEW 6 </td> </tr> <tr> ! <td><home> </td> <td> C:\Program Files\National Instruments\LabVIEW 6 </td> </tr> <tr> ! <td><vi.lib> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\vi.lib </td> </tr> <tr> ! <td><user.lib> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\user.lib </td> </tr> <tr> ! <td><instr.lib> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\instr.lib </td> </tr> <tr> ! <td><project> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\project </td> </tr> <tr> ! <td><resource> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\resource </td> </tr> <tr> ! <td><preferences> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\LabVIEW.ini </td> </tr> <tr> ! <td><temp> </td> <td> C:\Documents and Settings\username\Local Settings\Temp </td> </tr> <tr> ! <td><help> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\help </td> </tr> <tr> ! <td><file> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\wizard </td> </tr> <tr> ! <td><menus> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\menus </td> </tr> --- 36,84 ---- </tr> <tr> ! <td style="padding-right: 10" nowrap><application> </td> <td> C:\Program Files\National Instruments\LabVIEW 6 </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><home> </td> <td> C:\Program Files\National Instruments\LabVIEW 6 </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><vi.lib> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\vi.lib </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><user.lib> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\user.lib </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><instr.lib> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\instr.lib </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><project> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\project </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><resource> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\resource </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><preferences> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\LabVIEW.ini </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><temp> </td> <td> C:\Documents and Settings\username\Local Settings\Temp </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><help> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\help </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><file> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\wizard </td> </tr> <tr> ! <td style="padding-right: 10" nowrap><menus> </td> <td> C:\Program Files\National Instruments\LabVIEW 6\menus </td> </tr> Index: DEAB Revision File Dscr.htm =================================================================== RCS file: /cvsroot/opengtoolkit/deab/developer docs/DEAB Revision File Dscr.htm,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** DEAB Revision File Dscr.htm 6 Nov 2004 08:17:06 -0000 1.1 --- DEAB Revision File Dscr.htm 9 Nov 2004 10:12:20 -0000 1.2 *************** *** 5,9 **** <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> ! <title>DEAB File Description</title> </head> --- 5,9 ---- <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> ! <title>DEAB Revision File Description</title> </head> *************** *** 16,19 **** --- 16,23 ---- <p>This document describes parameters of a DEAB Revision file.</p> <p> </p> + <p>A Revision File is an optional file that DEAB can use to control build + versions and save general information on the last build status. A Revision File + can treat several Build Files. Information relating to each Build File is stored + in a unique section that has name of the Build File.</p> <p><strong>[<em>BuildFileName</em>]</strong><br> <a href="#Version">Version</a><br> *************** *** 23,34 **** <a href="#Warnings">Warnings</a><br> <a href="#Log_File">Log_File</a></p> <hr> <p><b><a name="Version" id="Version"></a><strong>[<em>BuildFileName</em>]</strong></b></p> <p><b>Version</b> = version string</p> ! <p><i>Version</i> is optional. If it is not specified, it is assumed to be ! version 0.0.0. If <i>File Format Version</i> is greater than the current DEAB ! version, a warning will be generated.</p> <p><u>Example:</u></p> ! <p>File Format Version = 1.0.0</p> --- 27,95 ---- <a href="#Warnings">Warnings</a><br> <a href="#Log_File">Log_File</a></p> + <p> </p> <hr> <p><b><a name="Version" id="Version"></a><strong>[<em>BuildFileName</em>]</strong></b></p> <p><b>Version</b> = version string</p> ! <p>The <i>Version</i> can accept an arbitrary string to identify a version of a ! target application. The <i>Version</i> is beyond of the DEAB ! control. However, DEAB can use a value of it to assign a version information to a ! specified control of a VI in a built application as a default value, so the ! application can obtain the <i>Version</i> string, <i><a href="#Build_Number">Build_Number</a></i> ! and <i><a href="#Log_File">Build_Date</a></i> at runtime (see <a href="DEAB%20File%20Dscr.htm" target="_blank">DEAB ! Build File Description</a>, <a href="DEAB%20File%20Dscr.htm#General: Version VI/Ctrl Name" target="_blank">Version ! Ctrl Name</a> topic for details).</p> ! <p>If the <i>Version</i> parameter is not specified in a Revision File, DEAB ! adds the parameter with a value of "0.0.0" and assumes the value as a ! current version of an application.<br> ! </p> <p><u>Example:</u></p> ! <p> Version = 1.0.0</p> ! ! ! <hr> ! <p><b><a name="Build_Number" id="Version0"></a><strong>[<em>BuildFileName</em>]</strong></b></p> ! <p><b>Build_Number</b> = integer</p> ! <p>DEAB increments the <i>Build_Number</i> parameter at the beginning of each ! build. DEAB can use a value of it to assign a version information to a ! specified control of a VI in a built application as a default value, so the ! application can obtain the <i><a href="#Version">Version</a></i> string, <i>Build_Number</i> ! and <i><a href="#Log_File">Build_Date</a></i> at runtime (see <a href="DEAB%20File%20Dscr.htm" target="_blank">DEAB ! Build File Description</a>, <a href="DEAB%20File%20Dscr.htm#General: Version VI/Ctrl Name" target="_blank">Version ! Ctrl Name</a> topic for details).</p> ! <p> If the <i>Build_Number</i> is not specified in a Revision File, it assimes ! to be zero.<br> ! </p> ! <hr> ! <p><b><a name="Build_Date" id="Version1"></a><strong>[<em>BuildFileName</em>]</strong></b></p> ! <p><b>Build_Date</b> = date/time string</p> ! <p>DEAB assign a date/time string to the <i>Build_Date</i> parameter at the ! beginning of each build. DEAB can use a value of it to assign a version information to a ! specified control of a VI in a built application as a default value, so the ! application can obtain the <i><a href="#Version">Version</a></i> string, <i><a href="#Build_Number">Build_Number</a></i> ! and <i>Build_Date</i> at runtime (see <a href="DEAB%20File%20Dscr.htm" target="_blank">DEAB ! Build File Description</a>, <a href="DEAB%20File%20Dscr.htm#General: Version VI/Ctrl Name" target="_blank">Version ! Ctrl Name</a> topic for details).<br> ! </p> ! <hr> ! <p><b><a name="Status" id="Version2"></a><strong>[<em>BuildFileName</em>]</strong></b></p> ! <p><b>Status</b> = OK/ERROR</p> ! <p><i>Status</i> parameter indicates a status of the last build. It equals ! "OK" if a build completed with no fatal-error. A value of ! "ERROR" indicates a fatal-error occurred during a build. Detailed ! information on the error can be found in a <i><a href="#Log_File">Log_File</a></i>.<br> ! </p> ! <hr> ! <p><b><a name="Warnings" id="Version3"></a><strong>[<em>BuildFileName</em>]</strong></b></p> ! <p><b>Warnings</b> = integer</p> ! <p><i>Warnings</i> parameter indicates a total number of non-fatal errors and ! warnings occurred during a build if <i>Status</i> is OK. Detailed information on ! non-fatal errors and warnings can be found in a <i><a href="#Log_File">Log_File</a></i>.<br> ! </p> ! <hr> ! <p><b><a name="Log_File" id="Version4"></a><strong>[<em>BuildFileName</em>]</strong></b></p> ! <p><b>Log_File</b> = file path</p> ! <p><i>Log_File</i> parameter indicates a complete path to a log file written ! during the last build.<br> ! </p> Index: DEAB Overview.htm =================================================================== RCS file: /cvsroot/opengtoolkit/deab/developer docs/DEAB Overview.htm,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** DEAB Overview.htm 6 Nov 2004 08:18:42 -0000 1.3 --- DEAB Overview.htm 9 Nov 2004 10:12:20 -0000 1.4 *************** *** 4,13 **** <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> ! <title>Untitled Document</title> </head> ! <body> <h3> DEAB Overview</h3> ! The Development Environment Application Builder (DEAB) is a tool similar to the <b>Save With Options</b> >> <b>Application Distribution</b> function of LabVIEW. However, the DEAB allows programmattic builds and also allows many more options like:<br> <ul> <li> Define top level and dynamic VIs that define the hierarchies to be built </li> --- 4,14 ---- <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> ! <title>DEAB Overview</title> </head> ! <body style="font-family: Verdana; font-size: 10pt"> <h3> DEAB Overview</h3> ! The Development Environment Application Builder (DEAB) is a tool similar to the <b>Save With Options</b> >> <b>Application Distribution</b> function of LabVIEW. However, the DEAB allows ! programmatic builds and also allows many more options like:<br> <ul> <li> Define top level and dynamic VIs that define the hierarchies to be built </li> *************** *** 26,30 **** <li><a href="DEAB Pathroots Dscr.htm">DEAB Pathroots</a></li> <li><a href="DEAB Release Notes 1.0.htm">DEAB 1.0 Release Notes</a></li> ! <li><a href="DEAB%20Pathroots%20Dscr.htm">DEAB Pathroots</a></li> </ul> </body> --- 27,31 ---- <li><a href="DEAB Pathroots Dscr.htm">DEAB Pathroots</a></li> <li><a href="DEAB Release Notes 1.0.htm">DEAB 1.0 Release Notes</a></li> ! <li><a href="DEAB%20Glossary.htm">DEAB Glossary</a></li> </ul> </body> Index: DEAB Glossary.htm =================================================================== RCS file: /cvsroot/opengtoolkit/deab/developer docs/DEAB Glossary.htm,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** DEAB Glossary.htm 5 Nov 2004 12:13:59 -0000 1.6 --- DEAB Glossary.htm 9 Nov 2004 10:12:20 -0000 1.7 *************** *** 69,84 **** Run-Time menu, <a href="#Shared_Library">Shared Library</a>, etc. </p> <p><a name="Revision_File"></a><b>Revision File</b> - A text file storing ! version information and status of the last build.<br> ! The version information includes a version string, the last build number and ! date/time of the last build. When a build starts, DEAB saves date/time of that ! and increments a build number in a Revision File (if any specified in the <a href="#Build_File">Build ! File</a>). A version string is user defined and it is beyond of the DEAB ! control. However, DEAB can use its value to assign a version information to a ! specified control of a VI in a built application as a default value, so the ! application can obtain the version (as well as a build number and build ! date/time) at runtime.<br> The build status information includes fatal and non-fatal errors status, and a ! name of <a href="#Log_File">Log File</a> written.<br> ! A single revision file can be used to serve several build files independently. </p> <p><a name="Shared_Library" id="Shared_Library"></a><b>Shared Library</b> - <font size="-1">A file that contains routines that can be dynamically loaded and shared by applications. In LabVIEW, shared libraries are called using the Call Library Function primitive.</font> In Windows shared libary files are called Dynamic Linked Libraries and have a *.dll file extension. In Linux, shared libraries have a *.so file extension. In Mac OS 9 shared libraries have a .shlb file extension and in Mac OS X, they have a *.framework file extension. </p> <p><a name="Source_Root" id="Source_Root"></a><b>Source Root</b> -The (configurable) path where the software product source files are kept. Source file paths are specified relative to the Source Root. </p> --- 69,78 ---- Run-Time menu, <a href="#Shared_Library">Shared Library</a>, etc. </p> <p><a name="Revision_File"></a><b>Revision File</b> - A text file storing ! version information and a status of the last build. The version information includes a version string, the last build number and ! date/time of the last build. The build status information includes fatal and non-fatal errors status, and a ! name of <a href="#Log_File">Log File</a> written. A single revision file can be used to serve several ! Build Files independently. See <a href="DEAB%20Revision%20File%20Dscr.htm" target="_blank">DEAB ! Revision File Description</a> for more information. </p> <p><a name="Shared_Library" id="Shared_Library"></a><b>Shared Library</b> - <font size="-1">A file that contains routines that can be dynamically loaded and shared by applications. In LabVIEW, shared libraries are called using the Call Library Function primitive.</font> In Windows shared libary files are called Dynamic Linked Libraries and have a *.dll file extension. In Linux, shared libraries have a *.so file extension. In Mac OS 9 shared libraries have a .shlb file extension and in Mac OS X, they have a *.framework file extension. </p> <p><a name="Source_Root" id="Source_Root"></a><b>Source Root</b> -The (configurable) path where the software product source files are kept. Source file paths are specified relative to the Source Root. </p> Index: DEAB File Dscr.htm =================================================================== RCS file: /cvsroot/opengtoolkit/deab/developer docs/DEAB File Dscr.htm,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** DEAB File Dscr.htm 6 Nov 2004 06:41:30 -0000 1.9 --- DEAB File Dscr.htm 9 Nov 2004 10:12:19 -0000 1.10 *************** *** 5,15 **** <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> ! <title>DEAB File Description</title> </head> <body style="font-family: Verdana; font-size: 10pt"> ! <p>DEAB<br> ! version 1.0.0<br> $Revision$<br> $Date$</p> --- 5,15 ---- <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> ! <title>DEAB Build File Description</title> </head> <body style="font-family: Verdana; font-size: 10pt"> ! <p>DEAB Build File Format<br> ! DEAB Version 1.0.0<br> $Revision$<br> $Date$</p> *************** *** 44,48 **** Version VI Name</a><br> <a href="#General: Version VI/Ctrl Name"> ! Version Ctrl Name</a></p> <p> --- 44,51 ---- Version VI Name</a><br> <a href="#General: Version VI/Ctrl Name"> ! Version Ctrl Name</a><br> ! <a href="#General: Apply New Password"> ! Apply New Password</a></p> ! <p> *************** *** 62,66 **** Convert Target to EXE<br> Remove Diagrams<br> ! Default Destination</p> <p><a href="#SupportFiles"><b>[SupportFiles N]</b></a><br> TargetDir<br> --- 65,70 ---- Convert Target to EXE<br> Remove Diagrams<br> ! Default Destination<br> ! Apply New Password</p> <p><a href="#SupportFiles"><b>[SupportFiles N]</b></a><br> TargetDir<br> *************** *** 87,91 **** <p><i>Revision File</i> is optional parameter that specifies a Revision File to be used. For more information on a Revision File, see <a href="DEAB%20Glossary.htm" target="_blank"> DEAB ! Glossary</a>. A <i>Revision File</i> may be either an absolute path, or a path relative to the <i><a href="#General: Project Root"> Project Root</a></i>. If a specified <i>Revision --- 91,96 ---- <p><i>Revision File</i> is optional parameter that specifies a Revision File to be used. For more information on a Revision File, see <a href="DEAB%20Glossary.htm" target="_blank"> DEAB ! Glossary</a> and <a href="DEAB%20Revision%20File%20Dscr.htm" target="_blank">DEAB ! Revision File Description</a>. A <i>Revision File</i> may be either an absolute path, or a path relative to the <i><a href="#General: Project Root"> Project Root</a></i>. If a specified <i>Revision *************** *** 177,188 **** renamed. If any source file is detected beneath a <i>Build Root</i>, the <i>Build Root</i> directory will not be renamed and a build terminates with a fatal ! error. ! </p> ! <p>[KS for JK] The correct meaning is that exactly <i> Build Root</i> is renamed ! </p> ! <p>[Prev. edition] ! </p> ! <p>If <i> New Build Root</i> key is equal to TRUE and a directory at<i><a href="#General: Build Root"> Build Root</a></i> exists when the build begins, the existing directory will be renamed with a date-time suffix and new directory at ! <i> Build Root</i> will be created for the active build. By default, the parameter is FALSE.<br> </p> <hr> --- 182,186 ---- renamed. If any source file is detected beneath a <i>Build Root</i>, the <i>Build Root</i> directory will not be renamed and a build terminates with a fatal ! error.<br> </p> <hr> *************** *** 252,256 **** <p><b><a name="General: Unsaved Changes"></a>[General]</b></p> <p><b>Unsaved Changes MsgBox</b> = True/False</p> ! <p><i>Unsaved Changes MsgBox</i> is optional. If it is TRUE and there is an unsaved VI (a VI has non-zero Modification Bitset property), a message box appears to ask a user to either continue or abort building. By default, it is TRUE.<br> </p> --- 250,255 ---- <p><b><a name="General: Unsaved Changes"></a>[General]</b></p> <p><b>Unsaved Changes MsgBox</b> = True/False</p> ! <p><i>Unsaved Changes MsgBox</i> is optional. If it is TRUE and there is an unsaved VI (a VI has ! a non-zero Modification Bitset property), a message box appears to ask a user to either continue or abort building. By default, it is TRUE.<br> </p> *************** *** 281,284 **** --- 280,305 ---- </p> <hr> + <p><b><a name="General: Apply New Password"></a>[General]</b></p> + <p><b>Apply New Password</b> = "string"</p> + <p>The <i>Apply New Password</i> is optional parameter that specifies a default + password to be applied to all target VIs of the build. If the parameter is + missed or a value of it is an empty string, no password will be applied by + default. Note that a <i><a href="#Destination">[Destination N]</a></i> section + may contain its own <i>Apply New Password</i> parameter that overrides the + default value specified in <i>[General]</i> section. + </p> + <p>A special case of a password is the <u>random</u> keyword that makes DEAB + generate random password of a desired length and use it as a default password. + Generic syntax of the <u>random</u> keyword is:<br> + "random:N"<br> + , where <u>random</u> is the case-insensitive keyword, and N is an optional + length of a password; by default a password length is equal to 32. + </p> + <p><u>Examples:</u></p> + <p>Apply New Password=""<br> + Apply New Password="MySecretPassword"<br> + Apply New Password="random:16"<br> + </p> + <hr> <p><b><a name="Top-Level VIs"></a>[Top Level VIs]</b></p> <p><b>keyname</b> = "VI path"</p> *************** *** 323,333 **** <b>Convert Target to EXE</b> = True/False<br> <b>Remove Diagrams</b> = True/False<br> ! <b>Default Destination</b> = True/False</p> <p><i>[Destination N]</i> sections should be named "Destination N", where "N" is an arbitrary unique integer. This allows to specify multiple ! Destination sections. A Destination with the least number (N) is to be used as a ! default destination if it is allowed by <i><a href="#General: LeastDestIsDefault">TheLeastNumberedDestinationIsDefault</a></i> ! option in <i>[General]</i> section.</p> ! <p>Every VI or CTL in the application source hierarchy which is located beneath <i> Source Dir</i> will be aggregated into <i> Target Dir</i>, except for those VIs and CTLs found beneath a subdirectory specified as a <i> Source Dir</i> of another Destination.</p> --- 344,352 ---- <b>Convert Target to EXE</b> = True/False<br> <b>Remove Diagrams</b> = True/False<br> ! <b>Default Destination</b> = True/False<br> ! <b>Apply New Password</b> = "string"</p> <p><i>[Destination N]</i> sections should be named "Destination N", where "N" is an arbitrary unique integer. This allows to specify multiple ! Destination sections. Every VI or CTL in the application source hierarchy which is located beneath <i> Source Dir</i> will be aggregated into <i> Target Dir</i>, except for those VIs and CTLs found beneath a subdirectory specified as a <i> Source Dir</i> of another Destination.</p> *************** *** 340,351 **** This keyword overrides both <i>Convert Target to LLB</i> and <i>Convert Target to EXE</i> keys.</p> ! <p>If <i>Convert Target to LLB</i> optional parameter is TRUE, the <i>Target Dir</i> is actually to be a LabVIEW library file with LLB extension. This setting may be overridden by the <i> Convert Target to EXE</i> setting and/or <u><KeepHierarchy></u> keyword.</p> ! <p>If <i>Convert Target to EXE</i> optional parameter is TRUE, the <i>Target Dir</i> is actually to be an executable file with EXE extension. This setting may be overridden by <u><KeepHierarchy></u> keyword.</p> ! <p>If <i>Remove Diagrams</i> optional parameter is TRUE, all VIs in this Destination will have their diagrams removed, during the build.</p> <p>If the <i>Default Destination</i> optional parameter is TRUE for a section, --- 359,370 ---- This keyword overrides both <i>Convert Target to LLB</i> and <i>Convert Target to EXE</i> keys.</p> ! <p>If the <i>Convert Target to LLB</i> optional parameter is TRUE, the <i>Target Dir</i> is actually to be a LabVIEW library file with LLB extension. This setting may be overridden by the <i> Convert Target to EXE</i> setting and/or <u><KeepHierarchy></u> keyword.</p> ! <p>If the <i>Convert Target to EXE</i> optional parameter is TRUE, the <i>Target Dir</i> 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 the <i>Default Destination</i> optional parameter is TRUE for a section, *************** *** 360,364 **** then a fatal error will be generated if any VI in the application hierarchy does not exist within the <i>Source Dir</i> of at least one <i>[Destination N]</i> ! section.<br> </p> <p><u>Example:</u></p> --- 379,397 ---- then a fatal error will be generated if any VI in the application hierarchy does not exist within the <i>Source Dir</i> of at least one <i>[Destination N]</i> ! section. ! </p> ! <p>The <i>Apply New Password</i> is optional parameter that may be used to apply ! a password string to all VIs of the destination. If the parameter is missed or a ! value of it is an empty string, DEAB uses a value of the <i><a href="#General: Apply New Password">Apply ! New Password</a> </i>parameter in the <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.<br> ! There are 2 special cases of a password string. If a password string is ! "none", it suppresses a default password (specified in <i><a href="#General: Apply New Password">[General]</a></i> ! section) for the destination. If a password string is either "random" ! or "random:N", where N is an integer, DEAB generates random ! password of a length N (32 by default) and applies it to all VIs of the destination. ! Note that both "none" and "random" keywords are ! case-insensitive.<br> </p> <p><u>Example:</u></p> *************** *** 370,373 **** --- 403,407 ---- Remove Diagrams=FALSE<br> Default Destination=TRUE<br> + Apply New Password="MySecretPassword"<br> <br> [Destination 1001]<br> *************** *** 378,381 **** --- 412,416 ---- Remove Diagrams=FALSE<br> Default Destination=FALSE<br> + Apply New Password=""<br> <br> [Destination 2001]<br> *************** *** 386,389 **** --- 421,425 ---- Remove Diagrams=FALSE<br> Default Destination=FALSE<br> + Apply New Password="random:16"<br> </p> <hr> |
