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

[cmake-commits at cmake.org]

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

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


Index: CMakeCommands.html
===================================================================
RCS file: /cvsroot/CMake/CMakeWeb/HTML/CMakeCommands.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- CMakeCommands.html	16 Feb 2007 11:00:10 -0000	1.42
+++ CMakeCommands.html	17 Mar 2007 10:00:11 -0000	1.43
@@ -1,4 +1,4 @@
-<h2>Documentation for Commands of CMake 2.4-patch 7 RC-4</h2>
+<h2>Documentation for Commands of CMake 2.4-patch 7 RC-5</h2>
 <ul>
   <li>
     <b><code>ADD_CUSTOM_COMMAND</code></b>: Add a custom build rule to the generated build system.<br>
@@ -135,7 +135,7 @@
     <pre>  FILE(WRITE filename "message to write"... )<br>  FILE(APPEND filename "message to write"... )<br>  FILE(READ filename variable)<br>  FILE(GLOB variable [RELATIVE path] [globbing expressions]...)<br>  FILE(GLOB_RECURSE variable [RELATIVE path] <br>       [globbing expressions]...)<br>  FILE(REMOVE [directory]...)<br>  FILE(REMOVE_RECURSE [directory]...)<br>  FILE(MAKE_DIRECTORY [directory]...)<br>  FILE(RELATIVE_PATH variable directory file)<br>  FILE(TO_CMAKE_PATH path result)<br>  FILE(TO_NATIVE_PATH path result)<br></pre>
     <p>WRITE will write a message into a file called 'filename'. It overwrites the file if it already exists, and creates the file if it does not exist.<br><p>APPEND will write a message into a file same as WRITE, except it will append it to the end of the file<br><p>NOTE: When using FILE WRITE and FILE APPEND, the produced file cannot be used as an input to CMake (CONFIGURE_FILE, source file ...) because it will lead to an infinite loop. Use CONFIGURE_FILE if you want to generate input files to CMake.<br><p>READ will read the content of a file and store it into the variable.<br><p>GLOB will generate a list of all files that match the globbing expressions and store it into the variable. Globbing expressions are similar to regular expressions, but much simpler. If RELATIVE flag is specified for an expression, the results will be returned as a relative path to the given path.<br><p>Examples of globbing expressions include:<br><pre>   *.cxx      - match all files with extension cxx<br>   *.vt?      - match all files with extension vta,...,vtz<br>   f[3-5].txt - match files f3.txt, f4.txt, f5.txt<br></pre>
     <p>GLOB_RECURSE will generate similar list as the regular GLOB, except it will traverse all the subdirectories of the matched directory and match the files.<br><p>Examples of recursive globbing include:<br><pre>   /dir/*.py  - match all python files in /dir and subdirectories<br></pre>
-    <p>MAKE_DIRECTORY will create a directory at the specified location<br><p>RELATIVE_PATH will determine relative path from directory to the given file.<br><p>TO_CMAKE_PATH will convert path into a cmake sytle path with unix /.  The input can be a single path or a system path like "$ENV{PATH}".  Note the double quotes around the ENV call TO_CMAKE_PATH only takes  one argument.<br><p>TO_NATIVE_PATH works just like TO_CMAKE_PATH, but will convert from  a cmake style path into the native path style \ for windows and / for UNIX.
+    <p>MAKE_DIRECTORY will create a directory at the specified location<br><p>RELATIVE_PATH will determine relative path from directory to the given file.<br><p>TO_CMAKE_PATH will convert path into a cmake style path with unix /.  The input can be a single path or a system path like "$ENV{PATH}".  Note the double quotes around the ENV call TO_CMAKE_PATH only takes  one argument.<br><p>TO_NATIVE_PATH works just like TO_CMAKE_PATH, but will convert from  a cmake style path into the native path style \ for windows and / for UNIX.
   </li>
   <li>
     <b><code>FIND_FILE</code></b>: Find the full path to a file.<br>