diff --git a/Web/Art/CMakeBanner.jpg b/Web/Art/CMakeBanner.jpg new file mode 100644 index 000000000..60c1dc9d4 Binary files /dev/null and b/Web/Art/CMakeBanner.jpg differ diff --git a/Web/Art/CMakeBanner.psd b/Web/Art/CMakeBanner.psd new file mode 100644 index 000000000..5640ac0e5 Binary files /dev/null and b/Web/Art/CMakeBanner.psd differ diff --git a/Web/Art/CMakeLogo.ppt b/Web/Art/CMakeLogo.ppt new file mode 100644 index 000000000..1ca31ad0e Binary files /dev/null and b/Web/Art/CMakeLogo.ppt differ diff --git a/Web/Art/CMakeLogo.psd b/Web/Art/CMakeLogo.psd new file mode 100644 index 000000000..1c6819751 Binary files /dev/null and b/Web/Art/CMakeLogo.psd differ diff --git a/Web/Art/SideBar.jpg b/Web/Art/SideBar.jpg new file mode 100644 index 000000000..d79460e0e Binary files /dev/null and b/Web/Art/SideBar.jpg differ diff --git a/Web/Art/SideBar.psd b/Web/Art/SideBar.psd new file mode 100644 index 000000000..ede3c0473 Binary files /dev/null and b/Web/Art/SideBar.psd differ diff --git a/Web/Art/acl.gif b/Web/Art/acl.gif new file mode 100644 index 000000000..47f623a2c Binary files /dev/null and b/Web/Art/acl.gif differ diff --git a/Web/Art/itkLogoSmallTransparentBackground.gif b/Web/Art/itkLogoSmallTransparentBackground.gif new file mode 100644 index 000000000..a16d5e610 Binary files /dev/null and b/Web/Art/itkLogoSmallTransparentBackground.gif differ diff --git a/Web/Art/nlm_logo.gif b/Web/Art/nlm_logo.gif new file mode 100644 index 000000000..f0554a523 Binary files /dev/null and b/Web/Art/nlm_logo.gif differ diff --git a/Web/Art/swooshSmall.gif b/Web/Art/swooshSmall.gif new file mode 100644 index 000000000..2ed9c2b49 Binary files /dev/null and b/Web/Art/swooshSmall.gif differ diff --git a/Web/HTML/About.html b/Web/HTML/About.html new file mode 100644 index 000000000..aac273a74 --- /dev/null +++ b/Web/HTML/About.html @@ -0,0 +1,134 @@ + + + + + + +
+ + + ++ + CMake is designed to support complex directory hierarchies and + applications dependent on several libraries. For example, CMake supports + projects consisting of multiple toolkits (i.e., libraries), where each + toolkit might contain several directories, and the application depends on + the toolkits plus additional code. CMake can also handle situations where + executables must be built in order to generate code that is then compiled + and linked into a final application. Because CMake is open source, and has + a simple, extensible design, CMake can be extended as necessary to support + new features. +
+ + Using CMake is simple. The build process is controlled by creating one or + more CMakeLists.txt files in each directory (including subdirectories) + that make up a project. Each CMakeLists.txt consists of one or more + commands. Each command has the form COMMAND (args...) where COMMAND is + the name of the command, and args is a white-space separated list of + arguments. CMake provides many pre-defined commands, but if you need to, + you can add your own commands. In addition, the advanced user can add + other makefile generators for a particular compiler/OS combination. + (While Unix and MSVC++ is supported currently, other developers are + adding other compiler/OS support.) You may wish to study the + examples page to see more + details. + +
+
+ cvs -d :pserver:anonymous@www.visualizationtoolkit.org:/vtk/cvsroot login
+ (respond with password vtk)
+
+ Follow this command by checking out the source code:
+ cvs -d :pserver:anonymous@www.visualizationtoolkit.org:/vtk/cvsroot co vtk
+
+ +
+ cvs -d :pserver:anonymous@public.kitware.com:/insight/cvsroot login
+ (respond with password insight)
+
+ Follow this command by checking out the source code:
+ cvs -d :pserver:anonymous@public.kitware.com:/insight/cvsroot co Insight
+
+ +
+ To use CVS, you must have it installed on your system. You may wish to + use the + Cygwin tools on Windows + platforms, or WinCVS which provides + a very nice GUI to CVS. +
+ The source is accessed by checking out a read-only version of the CMake + source code. (Only developers have write-access to the repository. Contact + Kitware at kitware@kitware.com if you require write access.) Use + the following commands. +
+ cvs -d :pserver:anonymous@public.kitware.com:/insight/cmakecvsroot login
+ (respond with password insight)
+
+ Follow this command by checking out the source code:
+ cvs -d :pserver:anonymous@public.kitware.com:/insight/cmakecvsroot co CMake
+
+
+ ![]() |
+ + National Library of Medicine (NLM) - Dr. Terry Yoo at NLM/NIH is + sponsoring the bulk of this work as part of the Insight segmentation + and registration toolkit (ITK). CMake was originally created to + support the multi-platform support necessary for ITK. + | +
+
+ ![]() |
+ + Insight Segmentation and Registration Toolkit - ITK is the original + sponsoring project for ITK. ITK is being funded by NLM to develop + cutting-edge algorithms and techniques to support the + + Visible Human Project. + | +
+
+ ![]() |
+ + Kitware, Inc. - Kitware personnel, primarily Bill Hoffman, Ken Martin, + and Brad King, were the principal developers of CMake. + | +
+
+ ![]() |
+ + Advanced Computing Lab at Los Alamos National Lab - Jim Ahrens + at LANL is technical project leader. He has supported the deployment + of CMake for building parallel processing applications. + | +
+ ![]() |
+|
+
+
+ The CMake testing dashboard is not currently available.
+ The nightly testing and release process will be available shortly.
+
+
+ |
+
+CMake was developed by +Kitware as part of the +NLM Insight Segmentation and +Registration Toolkit project. The Advanced Computing Lab at Los Alamos +National Lab also provided support in the context of their parallel +computation environment. Other sponsors include the Insight, +VTK, and +VXL +open source software communities. + +
+The goals for CMake include the following: +