[cmake-commits] king committed CMakeCommands.html 1.43 1.44

[cmake-commits at cmake.org]

Update of /cvsroot/CMake/CMakeWeb/HTML
In directory public:/mounts/ram/cvs-serv9812

Modified Files:
	CMakeCommands.html 
Log Message:
STYLE: Documentation update.


Index: CMakeCommands.html
===================================================================
RCS file: /cvsroot/CMake/CMakeWeb/HTML/CMakeCommands.html,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- CMakeCommands.html	17 Mar 2007 10:00:11 -0000	1.43
+++ CMakeCommands.html	18 May 2007 10:00:08 -0000	1.44
@@ -1,4 +1,4 @@
-<h2>Documentation for Commands of CMake 2.4-patch 7 RC-5</h2>
+<h2>Documentation for Commands of CMake 2.4-patch 7 RC-6</h2>
 <ul>
   <li>
     <b><code>ADD_CUSTOM_COMMAND</code></b>: Add a custom build rule to the generated build system.<br>
@@ -237,8 +237,8 @@
   </li>
   <li>
     <b><code>IF</code></b>: Conditionally execute a group of commands.<br>
-    <pre>  IF(expression)<br>    # THEN section.<br>    COMMAND1(ARGS ...)<br>    COMMAND2(ARGS ...)<br>    ...<br>  ELSE(expression)<br>    # ELSE section.<br>    COMMAND1(ARGS ...)<br>    COMMAND2(ARGS ...)<br>    ...<br>  ENDIF(expression)<br></pre>
-    <p>Evaluates the given expression.  If the result is true, the commands in the THEN section are invoked.  Otherwise, the commands in the ELSE section are invoked.  The ELSE section is optional.  Note that the same expression must be given to IF, ELSE, and ENDIF.  Long expressions can be used and the order or precedence is that the EXISTS, COMMAND, and DEFINED operators will be evaluated first. Then any EQUAL, LESS, GREATER, STRLESS, STRGREATER, STREQUAL, MATCHES will be evaluated. Then NOT operators and finally AND, OR operators will be evaluated. Possible expressions are:<br><pre>  IF(variable)<br></pre>
+    <pre>  IF(expression)<br>    # THEN section.<br>    COMMAND1(ARGS ...)<br>    COMMAND2(ARGS ...)<br>    ...<br>  ELSEIF(expression2)<br>    # ELSEIF section.<br>    COMMAND1(ARGS ...)<br>    COMMAND2(ARGS ...)<br>    ...<br>  ELSE(expression)<br>    # ELSE section.<br>    COMMAND1(ARGS ...)<br>    COMMAND2(ARGS ...)<br>    ...<br>  ENDIF(expression)<br></pre>
+    <p>Evaluates the given expression.  If the result is true, the commands in the THEN section are invoked.  Otherwise, the commands in the ELSE section are invoked.  The ELSEIF and ELSE sections are optional. You may have multiple ELSEIF clauses. Note that the same expression must be given to IF, and ENDIF.  Long expressions can be used and the order or precedence is that the EXISTS, COMMAND, and DEFINED operators will be evaluated first. Then any EQUAL, LESS, GREATER, STRLESS, STRGREATER, STREQUAL, MATCHES will be evaluated. Then NOT operators and finally AND, OR operators will be evaluated. Possible expressions are:<br><pre>  IF(variable)<br></pre>
     <p>True if the variable's value is not empty, 0, N, NO, OFF, FALSE, NOTFOUND, or &lt;variable&gt;-NOTFOUND.<br><pre>  IF(NOT variable)<br></pre>
     <p>True if the variable's value is empty, 0, N, NO, OFF, FALSE, NOTFOUND, or &lt;variable&gt;-NOTFOUND.<br><pre>  IF(variable1 AND variable2)<br></pre>
     <p>True if both variables would be considered true individually.<br><pre>  IF(variable1 OR variable2)<br></pre>