[opengtoolkit-cvs] deab/developer docs DEAB File Dscr.htm,1.7,1.8 news.txt,1.17,1.18

[Konstantin S. <ks...@us...>]

Update of /cvsroot/opengtoolkit/deab/developer docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14022/developer docs

Modified Files:
	DEAB File Dscr.htm news.txt 
Log Message:


Index: news.txt
===================================================================
RCS file: /cvsroot/opengtoolkit/deab/developer docs/news.txt,v
retrieving revision 1.17
retrieving revision 1.18
diff -C2 -d -r1.17 -r1.18
*** news.txt	5 Nov 2004 12:13:59 -0000	1.17
--- news.txt	6 Nov 2004 06:34:03 -0000	1.18
***************
*** 4,7 ****
--- 4,20 ----
  
  
+ *** 12:21 06.11.2004
+ 
+ - If 'New Build Root' parameter is TRUE and 'Build Root' directory exists, the Build Root is
+   to be renamed. However, there is a pitfall when a Build Root contains a source file beneath
+   it (e.g. if Build Root is the same as Source Root because both are pointed as an empty
+   string in a .deab file.
+   Now, DEAB tests if a source VI or resource file resides beneath a Build Root and generates
+   a fatal error if any found (note that it is only applicable if 'New Build Root' parameter
+   is TRUE).
+   DEAB File Dscr.htm file contains updated info in description of 'New Build Root'.
+ 
+ 
+ 
  *** 19:06 05.11.2004
  

Index: DEAB File Dscr.htm
===================================================================
RCS file: /cvsroot/opengtoolkit/deab/developer docs/DEAB File Dscr.htm,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** DEAB File Dscr.htm	5 Nov 2004 12:13:59 -0000	1.7
--- DEAB File Dscr.htm	6 Nov 2004 06:34:03 -0000	1.8
***************
*** 168,178 ****
  <p><b><a name="General: New Build Root"></a>[General]</b></p>
  <p><b>New Build Root</b>		= True/False</p>
- <p>[KS] the correct edition of this is:
- </p>
  <p>If <i> New Build Root</i> key is equal to TRUE and <i><a href="#General: Build Root">Build Root</a></i>
  directory exists when the build begins, the existing directory will be renamed with a date-time suffix and new
! <i>Build Root</i>  directory will be created for the active build. By default, the parameter is FALSE.
  </p>
! <p>[KS] i.e. exactly Build Root is renamed
  </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
--- 168,185 ----
  <p><b><a name="General: New Build Root"></a>[General]</b></p>
  <p><b>New Build Root</b>		= True/False</p>
  <p>If <i> New Build Root</i> key is equal to TRUE and <i><a href="#General: Build Root">Build Root</a></i>
  directory exists when the build begins, the existing directory will be renamed with a date-time suffix and new
! <i>Build Root</i>  directory will be created for the active build. By default, the
! <i>New Build Root</i> is FALSE.
  </p>
! <p>Note that <i><a href="#General: Build Root">Build Root</a></i>
!  directory may contain neither a source VI nor a resource file beneath it to be
! 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