+
+ CMake is designed to support complex directory hierarchies and @@ -100,7 +104,7 @@ vlink="#000000" alink="#000000"> adopted CMake as their build environment, contributing many essential features. Brad King added several features in order to support the CABLE automated wrapping environment and - gcc-XML, and + GCC-XML, and GE Corporate R&D required support of their testing infrastructure (the quality dashboard). Other features were added by Ken Martin to support the transition of VTK's @@ -118,8 +122,8 @@ vlink="#000000" alink="#000000"> list. There is some existing documentation, but until later in 2001 the documentation should be treated with caution. Please go to the documentation for more - information. - + information. Also, see the example + found here. diff --git a/Web/HTML/Documentation.html b/Web/HTML/Documentation.html index ad726fb7c..74b0dbba1 100644 --- a/Web/HTML/Documentation.html +++ b/Web/HTML/Documentation.html @@ -27,8 +27,8 @@ vlink="#000000" alink="#000000"> will use CMake in preference to the current build environment. VTK is a very large system for 3D graphics and visualization consisting of approximately 700 classes and hundreds of thousands of lines of executable - code. It fully exploits CMake's capabilities because of the automated - "wrapping" process that automatically generates interface code to Tcl, + code. It fully exploits CMake's capabilities due to the automated + "wrapping" process that generates interface code to Tcl, Python, and Java from the C++ header files.
cvs -d :pserver:anonymous@www.visualizationtoolkit.org:/vtk/cvsroot login
@@ -39,7 +39,7 @@ vlink="#000000" alink="#000000">
diff --git a/Web/HTML/Examples.html b/Web/HTML/Examples.html index 9ba12dcd6..2c2a89765 100644 --- a/Web/HTML/Examples.html +++ b/Web/HTML/Examples.html @@ -15,8 +15,57 @@ vlink="#000000" alink="#000000">
+ There are three directories involved. The top level directory has two + subdirectories called ./Demo and ./Hello. In the directory ./Hello, a + library is built. In the directory ./Demo, an executable is built by + linking to the library. A total of three CMakeList.txt files are + created: one for each directory. +
+ The first, top-level directory contains the following CMakeLists.txt file. +
+# The name of our project is "HELLO". CMakeLists files in this project can
+# refer to the root source directory of the project as ${HELLO_SOURCE_DIR} and
+# to the root binary directory of the project as ${HELLO_BINARY_DIR}.
+PROJECT(HELLO)
+# Recurse into the "Hello" and "Demo" subdirectories. This does not actually
+# cause another cmake executable to run. The same process will walk through
+# the project's entire directory structure.
+SUBDIRS(Hello Demo)
+
+ Then for each subdirectory listed in the SUBDIRS command, CMakeLists.txt
+ files are created. In the ./Hello directory, the following CMakeLists.txt
+ file is created:
+ +# Create a library called "Hello" which includes the source file "hello.cxx". +# The extension is already found. Any number of sources could be listed here. +ADD_LIBRARY(Hello hello) ++ Finally, in the ./Demo directory, the third and final CMakeLists.txt file + is created: +
+# Make sure the compiler can find include files from our Hello library.
+INCLUDE_DIRECTORIES(${HELLO_SOURCE_DIR}/Hello)
+
+# Make sure the linker can find the Hello library once it is built.
+LINK_DIRECTORIES(${HELLO_BINARY_DIR}/Hello)
+
+# Add executable called "helloDemo" that is built from the source files
+# "demo.cxx" and "demo_b.cxx". The extensions are automatically found.
+ADD_EXECUTABLE(helloDemo demo demo_b)
+
+# Link the executable to the Hello library.
+TARGET_LINK_LIBRARIES(helloDemo Hello)
+
+ CMake when executed in the top-level directory will process the
+ CMakeLists.txt file and then descend into the listed subdirectories.
+ Variables, include paths, library paths, etc. are inherited. Depending
+ on the system, makefiles (Unix) or workspaces/projects (MSVC) will be
+ built. These can then be used in the usual way to build the code.