Removing Web directory from CMake. It is moving to a separate, parallel CVS module called "CMakeWeb"
This commit is contained in:
Brad King
parent
9cce835900
commit
1c15dd408e
Binary file not shown.
|
Before Width: | Height: | Size: 19 KiB |
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 45 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.2 KiB |
Binary file not shown.
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 8.4 KiB |
Binary file not shown.
BIN
Web/Art/acl.gif
BIN
Web/Art/acl.gif
Binary file not shown.
|
Before Width: | Height: | Size: 700 B |
BIN
Web/Art/asci.gif
BIN
Web/Art/asci.gif
Binary file not shown.
|
Before Width: | Height: | Size: 2.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.8 KiB |
|
|
@ -1,114 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
|
||||
<font size=5>CMake </font> is an extensible, open-source system that
|
||||
manages the build process in an operating system and compiler independent
|
||||
manner. Unlike many cross-platform systems, CMake is designed to be used
|
||||
in conjunction with the native build environment. Simple configuration
|
||||
files placed in each source directory (called CMakeLists.txt files) are
|
||||
used to generate standard build files (e.g., makefiles on Unix and
|
||||
projects/workspaces in Windows MSVC) which are used in the usual
|
||||
way. CMake can compile source code, create libraries, generate wrappers,
|
||||
and build executables in arbitrary combinations. CMake supports in-place
|
||||
and out-of-place builds, and can therefore support multiple builds from a
|
||||
single source tree. CMake also supports static and dynamic library
|
||||
builds. Another nice feature of CMake is that it generates a cache file
|
||||
that is designed to be used with a graphical editor. For example, when
|
||||
CMake runs, it locates include files, libraries, and executable, and may
|
||||
encounter optional build directives. This information is gathered into
|
||||
the cache, which may be changed by the user prior to the generation of
|
||||
the native build files. (The following figure is the CMake cache GUI in
|
||||
the Windows MSVC environment.)
|
||||
<div align="center">
|
||||
<img src="/CMake/Art/CMakeGUI.jpg" width=400 height=276
|
||||
border=0 alt="">
|
||||
</div>
|
||||
<P>
|
||||
|
||||
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.
|
||||
<P>
|
||||
|
||||
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
|
||||
<a href="/CMake/HTML/Examples.html">examples</a> page to see more
|
||||
details.
|
||||
|
||||
<h3>The Origins of CMake</h3> CMake was created in response to the need
|
||||
for a powerful, cross-platform build environment for the Insight
|
||||
Segmentation and Registration Toolkit (ITK) funded by NLM as part of the
|
||||
Visible Human Project. It was influenced by an earlier system called
|
||||
<b>pcmaker</b> created by Ken Martin and other developers to support the
|
||||
<a href="http://public.kitware.com/vtk.html">Visualization Toolkit
|
||||
(VTK)</a> open source 3D graphics and visualization system. To create
|
||||
CMake, Bill Hoffman at Kitware incorporated some key ideas from pcmaker,
|
||||
and added many more of his own, with the thought to adopt some of the
|
||||
functionality of the Unix
|
||||
<b>configure</b> tool. The initial CMake implementation was mid-2000,
|
||||
with acclerated development occuring in early 2001. Many improvements
|
||||
were due to the influences of other developers incorporating CMake into
|
||||
their own systems. For example, the
|
||||
<a href="http://www.robots.ox.ac.uk/~vxl/">VXL</a> software community
|
||||
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
|
||||
<a href="http://public.kitware.com/GCC_XML">GCC-XML</a>, and
|
||||
GE Corporate R&D required support of their testing infrastructure
|
||||
(the <a href="http://public.kitware.com/Insight/Testing/HTML/TestingResults/Dashboard/MostRecentResults-Nightly/Dashboard.html">quality dashboard</a>).
|
||||
Other features were added to support the transition of VTK's
|
||||
build environment to CMake, and to support ParaView, a parallel
|
||||
visualization system to support the
|
||||
<a href="http://www.acl.lanl.gov/">Advanced Computing Lab</a> at Los Alamos
|
||||
National Laboratory.
|
||||
|
||||
<h3>How Do I Learn CMake?</h3> CMake is a young and rapidly growing
|
||||
system. It has already seen extensive use in very large software systems
|
||||
such as VTK, VXL, and ITK, and is therefore, quite
|
||||
stable. Unfortuneately, the pace of development has outstripped the pace
|
||||
of documentation. As a result, the best way to learn about CMake is to
|
||||
study existing CMake installations, and to rely on the CMake mailing
|
||||
list. There is some existing documentation, but until later in 2001 the
|
||||
documentation should be treated with caution. Please go to the
|
||||
<a href="/CMake/HTML/Documentation.html">documentation</a> for more
|
||||
information. Also, see the <a href="/CMake/HTML/Examples.html">example</a>
|
||||
found here.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,68 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>CMake documentation </font> is available as follows.
|
||||
<ul>
|
||||
<li>As a <a href="/CMake/HTML/CMake.pdf">PDF file</a>.
|
||||
<li>As a <a href="/CMake/HTML/CMake.rtf">RTF file</a>. (This can
|
||||
be opened by Word and many other systems.)
|
||||
</ul>
|
||||
<p>
|
||||
For additional information, refer to the
|
||||
CMake mailing list, or study an existing implementation (such as
|
||||
<a href="http://public.kitware.com/Insight">ITK</a> or
|
||||
<a href="http://public.kitware.com/vtk.html">VTK</a>). You can obtain
|
||||
access to this code as follows.
|
||||
<P>
|
||||
<h3>To obtain access to the VTK CVS repository:</h3>
|
||||
This repository is the "experimental" CMake-based environment. VTK 4.0
|
||||
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 due to the automated
|
||||
"wrapping" process that generates interface code to Tcl,
|
||||
Python, and Java from the C++ header files.
|
||||
<p>
|
||||
<b>cvs -d :pserver:anonymous@www.visualizationtoolkit.org:/vtk/cvsroot login</b><br>
|
||||
(respond with password vtk)
|
||||
<p>
|
||||
Follow this command by checking out the source code:<br>
|
||||
<b>cvs -d :pserver:anonymous@www.visualizationtoolkit.org:/vtk/cvsroot co vtknew</b>
|
||||
<p>
|
||||
|
||||
<h3>To obtain access to the ITK CVS repository:</h3>
|
||||
Insight (ITK) is the first project to adopt CMake. It is heavily templated
|
||||
C++ code using the generic programming style. It has an especially nice
|
||||
testing environment driven by CMake.
|
||||
<p>
|
||||
<b>cvs -d :pserver:anonymous@public.kitware.com:/insight/cvsroot login</b><br>
|
||||
(respond with password insight)
|
||||
<p>
|
||||
Follow this command by checking out the source code:<br>
|
||||
<b>cvs -d :pserver:anonymous@public.kitware.com:/insight/cvsroot co Insight</b>
|
||||
<p>
|
||||
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,52 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>Download </font>the
|
||||
<a href="http://public.kitware.com/CMake/CMSetup.exe">
|
||||
precompiled binary for Windows</a> or
|
||||
download the source code by using CVS. CVS is a source
|
||||
code revision control system used by many participants in the open-source
|
||||
community. There is currently no method to obtain the software as a
|
||||
packaged zip or tar file. Packaged releases will become available in
|
||||
the near future.
|
||||
<p>
|
||||
To use CVS, you must have it installed on your system. You may wish to
|
||||
use the
|
||||
<a href="http://sources.redhat.com/cygwin/">Cygwin</a> tools on Windows
|
||||
platforms, or <a href="http://www.wincvs.org">WinCVS</a> which provides
|
||||
a very nice GUI to CVS.
|
||||
<p>
|
||||
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.
|
||||
<p>
|
||||
<b>cvs -d :pserver:anonymous@public.kitware.com:/CMake/cvsroot login</b><br>
|
||||
(respond with password cmake)
|
||||
<p>
|
||||
Follow this command by checking out the source code:<br>
|
||||
<b>cvs -d :pserver:anonymous@public.kitware.com:/CMake/cvsroot co CMake</b>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,81 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>The following example </font> demonstrates some key ideas
|
||||
of CMake. (You may wish to download this
|
||||
<a href="/CMake/HTML/cmakeExample.tar.gz">example code</a> and try it
|
||||
out for yourself.) Make sure that you have CMake installed prior to
|
||||
running this example (go <a href="/CMake/HTML/Install.html">here</a>
|
||||
for instructions).
|
||||
<p>
|
||||
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.
|
||||
<p>
|
||||
The first, top-level directory contains the following CMakeLists.txt file.
|
||||
<pre>
|
||||
# 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)
|
||||
</pre>
|
||||
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:
|
||||
<pre>
|
||||
# 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)
|
||||
</pre>
|
||||
Finally, in the ./Demo directory, the third and final CMakeLists.txt file
|
||||
is created:
|
||||
<pre>
|
||||
# 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)
|
||||
</pre>
|
||||
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.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>The CMake FAQ </font> is not yet available.
|
||||
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,52 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
|
||||
<font size=5>A Summary Of Features</font><br> CMake is an extensible,
|
||||
open-source system that has several powerful features. These include:
|
||||
<ul>
|
||||
<li>Supports complex, large build environments. CMake has been
|
||||
proven in several large projects.</li>
|
||||
<li>Generates native build files (e.g., makefiles on Unix;
|
||||
workspaces/projects on MS Visual C++). Therefore standard
|
||||
tools can be used on any platform/compiler configuration.</li>
|
||||
<li>Has powerful commands include the ability to locate
|
||||
include files, libraries, executables; include external
|
||||
CMake files that encapsulate standard functionality;
|
||||
interfaces to testing systems; supports recursive
|
||||
directory traversal with variable inheritance; can run
|
||||
external programs; supports conditional builds; supports
|
||||
regular expression expansion; and so on.</li>
|
||||
<li>Supports in-place and out-of-place builds. Multiple
|
||||
compilation trees are possible from a single source tree.</li>
|
||||
<li>Can be easily extended to add new features.</li>
|
||||
<li>CMake is open source.</li>
|
||||
<li>CMake operates with a cache designed to be interfaced with
|
||||
a graphical editor. The cache provides optional interaction
|
||||
to conditionally control the build process.</li>
|
||||
</ul>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
<head>
|
||||
<title>CMake Cross Platform Make</title>
|
||||
<META NAME="keywords" CONTENT="Software, compile, make, build, cross-platform">
|
||||
<META NAME="description" CONTENT="CMake is an open-source,
|
||||
cross-platfom build environment. It supports native build processes
|
||||
on Unix and Windows platforms under a variety of compilers.">
|
||||
<META NAME="rating" CONTENT="General">
|
||||
<META NAME="ROBOTS" CONTENT="ALL">
|
||||
<link rel="stylesheet" href="/CMake/HTML/Style.css" type="text/css">
|
||||
</head>
|
||||
|
|
@ -1,39 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>Install </font> CMake differently depending on the
|
||||
operating system.
|
||||
<ul>
|
||||
<li>On Unix, you would perform the following:<pre>
|
||||
./configure
|
||||
make
|
||||
make install </pre>
|
||||
|
||||
<li>On Windows MSVC systems, find the CMakeSetup.dsw workspace and
|
||||
compile that project. (Note: pre-compiled binaries will be
|
||||
available shortly.)
|
||||
</ul>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>The CMake mailing list </font>is the principal means of
|
||||
communications among developers. Please go
|
||||
<a href="http://public.kitware.com/mailman/listinfo/cmake">
|
||||
here</a> to subscribe to the list. Instructions are given to
|
||||
receive an archive version of the list; as well as to manage
|
||||
and unsubscribe from the list.
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
|
||||
<font size=5>Current news </font>is listed in the following. Please visit the
|
||||
CMake mailing list and archives for detailed information.
|
||||
<ul>
|
||||
<li>CMake Release 0.2 available in July, 2001. This release is to
|
||||
include precompiled binaries and install shield for the Windows
|
||||
MSVC environment.
|
||||
<li>VTK 4.0 (release in late 2001) will adopt CMake as its build
|
||||
environment. A working CVS repository is currently functioning
|
||||
with CMake in preparation for the change.
|
||||
<li>VXL computer vision/image processing system adopts CMake as its
|
||||
build environment.
|
||||
<li>Insight segmentation and registration toolkit (ITK) supports
|
||||
development of the CMake environment.
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
<td width="150" height="600" valign="top"
|
||||
background="/CMake/Art/SideBar.jpg">
|
||||
<a href="/CMake/index.html"> Home</a><br><br>
|
||||
<a href="/CMake/HTML/About.html"> About</a><br><br>
|
||||
<a href="/CMake/HTML/Features.html"> Features</a><br><br>
|
||||
<a href="/CMake/HTML/Sponsors.html"> Sponsors</a><br><br>
|
||||
<a href="/CMake/HTML/Download.html"> Download</a><br><br>
|
||||
<a href="/CMake/HTML/Install.html"> Install</a><br><br>
|
||||
<a href="/CMake/HTML/Examples.html"> Example</a><br><br>
|
||||
<a href="/CMake/HTML/Documentation.html"> Documentation</a><br><br>
|
||||
<a href="/CMake/HTML/FAQ.html"> FAQ</a><br><br>
|
||||
<a href="/CMake/HTML/MailingLists.html"> Mailing Lists</a><br><br>
|
||||
<a href="/CMake/Testing/HTML/TestingResults/Dashboard/MostRecentResults-Nightly/Dashboard.html"> Testing</a><br><br>
|
||||
<a href="/CMake/HTML/TestingSetup.html"> Testing Setup</a><br><br>
|
||||
<a href="/CMake/HTML/News.html"> News</a><br><br>
|
||||
</td>
|
||||
|
||||
|
|
@ -1,90 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>Many generous sponsors and contributors</font>
|
||||
have supported this work. NLM continues to provide executive leadership in the
|
||||
administion of the project. The supporting agencies and institutes supporting
|
||||
this work include:<br><br><br>
|
||||
<dd>
|
||||
<TABLE cellpadding="8" border="0">
|
||||
|
||||
<TR>
|
||||
<TD align=right valign=middle>
|
||||
<A HREF="http://www.nlm.nih.gov">
|
||||
<img src="/CMake/Art/nlm_logo.gif" ALT="NLM logo" WIDTH=50 HEIGHT=50
|
||||
ALIGN=middle border=0></a></TD>
|
||||
<TD align=left valign=middle width=375>
|
||||
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
|
||||
<a href="http://public.kitware.com/Insight">(ITK)</a>.
|
||||
CMake was originally created for
|
||||
the multi-platform support necessary for ITK.
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD align=right valign=middle>
|
||||
<A HREF="http://public.kitware.com/Insight">
|
||||
<img src="/CMake/Art/itkLogoSmallTransparentBackground.gif" ALT="ITK logo"
|
||||
ALIGN=middle border=0></a></TD>
|
||||
<TD align=left valign=middle width=375>
|
||||
Insight Segmentation and Registration Toolkit - ITK is the original
|
||||
sponsoring project for CMake. ITK is being funded by NLM to develop
|
||||
cutting-edge algorithms and techniques to support the
|
||||
<a href="http://www.nlm.nih.gov/research/visible/visible_human.html">
|
||||
Visible Human Project.</a>
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD align=right valign=middle>
|
||||
<A HREF="http://www.kitware.com">
|
||||
<img src="/CMake/Art/swooshSmall.gif" ALT="Kitware logo"
|
||||
ALIGN=middle border=0></a></TD>
|
||||
<TD align=left valign=middle width=375>
|
||||
Kitware, Inc. - Kitware personnel, primarily Bill Hoffman, Ken Martin,
|
||||
and Brad King, were the principal developers of CMake.</A>
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD align=right valign=middle>
|
||||
<A HREF="http://www.acl.lanl.gov/">
|
||||
<img src=/CMake/Art/asci_little.gif ALT="ASCI VIEWS Logo"
|
||||
ALIGN=middle border=0></a></TD>
|
||||
<TD align=left valign=middle width=375>
|
||||
<a href="http://www.asci.doe.gov/scs/views.htm">ASCI VIEWS Project</a> -
|
||||
Jim Ahrens at the Advanced Computing Laboratory at Los Alamos National
|
||||
Lab is technical project leader. He has supported the deployment of
|
||||
CMake for building parallel processing applications.
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
</TABLE>
|
||||
</dd>
|
||||
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,41 +0,0 @@
|
|||
<head>
|
||||
<STYLE TYPE="text/css">
|
||||
<!--
|
||||
Body {
|
||||
font-family : verdana, tahoma, sans-serif;
|
||||
font-size : 9pt;
|
||||
color : black;
|
||||
}
|
||||
|
||||
Table {
|
||||
font-family : verdana, tahoma, sans-serif;
|
||||
font-size : 9pt;
|
||||
color : black;
|
||||
}
|
||||
|
||||
Table, TD {
|
||||
font-family : verdana, tahoma, sans-serif;
|
||||
font-size : 9pt;
|
||||
color : black;
|
||||
background-repeat : no-repeat;
|
||||
}
|
||||
|
||||
P {font-family : verdana, tahoma, sans-serif; font-size : 9pt;
|
||||
color: black; }
|
||||
|
||||
a {
|
||||
Font-Family : verdana, tahoma, sans-serif;
|
||||
Font-Size : 8pt;
|
||||
Font-Style : normal;
|
||||
text-decoration : none;
|
||||
color : blue;
|
||||
}
|
||||
|
||||
a:hover {
|
||||
color : black;
|
||||
Font-Style : bold;
|
||||
text-decoration : underline;
|
||||
}
|
||||
-->
|
||||
</STYLE>
|
||||
</head>
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
<table width="720" cellspacing="0" cellpadding="8" border="0">
|
||||
<tr>
|
||||
<td colspan="2">
|
||||
<img src="/CMake/Art/CMakeBanner.jpg" width=620 height=150
|
||||
border=0 alt="">
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -1,106 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>
|
||||
|
||||
If you would like to contribute to the CMake project by building a
|
||||
nightly dashboard build, you can follow these instructions.
|
||||
<ul>
|
||||
<li>Obtain a copy of the Dart client. http://public.kitware.com/Dart
|
||||
<br>
|
||||
cvs -d :pserver:anonymous@public.kitware.com:/Dart/cvsroot login
|
||||
(password is dart)
|
||||
<br>
|
||||
cvs -d :pserver:anonymous@public.kitware.com:/Dart/cvsroot co Dart
|
||||
<br>
|
||||
<li> install tcl.
|
||||
<li> configure your CMake build to find Tcl and Dart.
|
||||
<li> test your setup by typing make Experimental, then check the CMake dashboard in the next hour to see if your results are availiable.
|
||||
</ul>
|
||||
|
||||
Once you are able to submit experimental builds, the next step is setting up a nightly build. The nightly build works in almost the same way, but
|
||||
needs to be run each night by crontab or some other scheduling program. Getting environment variables correct can be difficult. Several examples are included here.
|
||||
|
||||
<ul>
|
||||
<li> Windows Visual C++ 6.0 Nightly build
|
||||
<br>
|
||||
cmakeNightlyVC.sh - A cygwin shell script to build a cmake dashboard.
|
||||
<PRE>
|
||||
cd //c/hoffman/Dart
|
||||
cvs update -dAP
|
||||
cd //c/hoffman/CMake
|
||||
cvs update -dAP
|
||||
cd //c/hoffman
|
||||
rm -rf CMake-vc-dashboard
|
||||
mkdir CMake-vc-dashboard
|
||||
cd CMake-vc-dashboard
|
||||
echo -e DART_ROOT:PATH=c:/Hoffman/Dart\\nMAKEPROGRAM:FILEPATH=msdev > CMakeCache.txt
|
||||
/cygdrive/c/hoffman/CMake/Source/cmake ../CMake
|
||||
msdev CMake.dsw /MAKE "Nightly - Win32 Debug" /BUILD
|
||||
</PRE>
|
||||
<br>
|
||||
cmakeNightlyVC.bat - A windows batch file that can run cmakeNightlyVC.sh and be used from the microsoft program scheduler.
|
||||
<PRE>
|
||||
bash --login //c/Hoffman/cmakeNightlyVC.sh
|
||||
</PRE>
|
||||
<br>
|
||||
dashboardCMake.csh -- a csh script to build cmake for a sun
|
||||
<PRE>
|
||||
#!/bin/csh
|
||||
cd ${HOME}/Dart
|
||||
cvs update -dAP
|
||||
cd ${HOME}/CMake
|
||||
cvs update -dAP
|
||||
cd ${HOME}
|
||||
# clean the entire build directory
|
||||
rm -rf CMake-CC-dashboard
|
||||
mkdir CMake-CC-dashboard
|
||||
cd CMake-CC-dashboard
|
||||
# preload the Dart path into the cache
|
||||
echo DART_ROOT:PATH=/disk2/home/hoffman/Dart > CMakeCache.txt
|
||||
setenv CXX CC
|
||||
setenv CC cc
|
||||
setenv CXXFLAGS ""
|
||||
../CMake/configure
|
||||
gmake Nightly
|
||||
</PRE>
|
||||
</PRE>
|
||||
<br>dashboardCronEntry.csh -- a csh script that can be run from cron
|
||||
<PRE>
|
||||
<PRE>
|
||||
#!/bin/csh
|
||||
/bin/rm -f nightlyBuild.out
|
||||
csh ${HOME}/dashboardCMake.csh > nightlyBuild.out
|
||||
</PRE>
|
||||
</PRE
|
||||
<br> contab entry for above
|
||||
<PRE>
|
||||
<PRE>
|
||||
# do a nightly cmake
|
||||
0 4 * * * /disk2/home/hoffman/cronRunTests
|
||||
</PRE>
|
||||
</PRE>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,108 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" >
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="550" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>Help improve the quality of CMake</font> by running a
|
||||
nightly dashboard build on your machine. If you would like to contribute
|
||||
to the CMake project by building a
|
||||
nightly dashboard build, you can follow these instructions.
|
||||
<ul>
|
||||
<li>Obtain a copy of the Dart (<a href="http://public.kitware.com/Dart">http://public.kitware.com/Dart</a>) client from cvs.
|
||||
<br>
|
||||
cvs -d :pserver:anonymous@public.kitware.com:/Dart/cvsroot login
|
||||
(password is dart)
|
||||
<br>
|
||||
cvs -d :pserver:anonymous@public.kitware.com:/Dart/cvsroot co Dart
|
||||
<br>
|
||||
<li> Install tcl.
|
||||
<li> Configure your CMake build to find Tcl and Dart.
|
||||
<li> Test your setup by typing make Experimental, then check the CMake dashboard in the next hour to see if your results are available.
|
||||
</ul>
|
||||
|
||||
Once you are able to submit experimental builds, the next step is setting up a nightly build. The nightly build works in almost the same way, but
|
||||
needs to be run each night by crontab or some other scheduling program. Getting environment variables correct can be difficult. Several examples are included here.
|
||||
<h2>Examples</h2>
|
||||
<ul>
|
||||
<li> Windows Visual C++ 6.0 Nightly build
|
||||
<br>
|
||||
cmakeNightlyVC.sh - A cygwin shell script to build a cmake dashboard.
|
||||
<PRE>
|
||||
cd //c/hoffman/Dart
|
||||
cvs update -dAP
|
||||
cd //c/hoffman/CMake
|
||||
cvs update -dAP
|
||||
cd //c/hoffman
|
||||
rm -rf CMake-vc-dashboard
|
||||
mkdir CMake-vc-dashboard
|
||||
cd CMake-vc-dashboard
|
||||
echo -e DART_ROOT:PATH=c:/Hoffman/Dart\\nMAKEPROGRAM:FILEPATH=msdev > CMakeCache.txt
|
||||
/cygdrive/c/hoffman/CMake/Source/cmake ../CMake
|
||||
msdev CMake.dsw /MAKE "Nightly - Win32 Debug" /BUILD
|
||||
</PRE>
|
||||
<br>
|
||||
cmakeNightlyVC.bat - A windows batch file that can run cmakeNightlyVC.sh and be used from the microsoft program scheduler.
|
||||
<PRE>
|
||||
bash --login //c/Hoffman/cmakeNightlyVC.sh
|
||||
</PRE>
|
||||
<br>
|
||||
<li> Solaris CC crontab scripts
|
||||
<br>
|
||||
dashboardCMake.csh -- a csh script to build cmake for a sun
|
||||
<PRE>
|
||||
#!/bin/csh
|
||||
cd ${HOME}/Dart
|
||||
cvs update -dAP
|
||||
cd ${HOME}/CMake
|
||||
cvs update -dAP
|
||||
cd ${HOME}
|
||||
# clean the entire build directory
|
||||
rm -rf CMake-CC-dashboard
|
||||
mkdir CMake-CC-dashboard
|
||||
cd CMake-CC-dashboard
|
||||
# preload the Dart path into the cache
|
||||
echo DART_ROOT:PATH=/disk2/home/hoffman/Dart > CMakeCache.txt
|
||||
setenv CXX CC
|
||||
setenv CC cc
|
||||
setenv CXXFLAGS ""
|
||||
../CMake/configure
|
||||
gmake Nightly
|
||||
</PRE>
|
||||
</PRE>
|
||||
<br>dashboardCronEntry.csh -- a csh script that can be run from cron
|
||||
<PRE>
|
||||
<PRE>
|
||||
#!/bin/csh
|
||||
/bin/rm -f nightlyBuild.out
|
||||
csh ${HOME}/dashboardCMake.csh > nightlyBuild.out
|
||||
</PRE>
|
||||
</PRE
|
||||
<br> contab entry for above
|
||||
<PRE>
|
||||
<PRE>
|
||||
# do a nightly cmake
|
||||
0 4 * * * /disk2/home/hoffman/dashboardCronEntry.csh
|
||||
</PRE>
|
||||
</PRE>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
Binary file not shown.
|
|
@ -1,73 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Head.html"-->
|
||||
|
||||
<body bgcolor="#FFFFFF" leftmargin=0 topmargin=0 text="black" link="#0000FF"
|
||||
vlink="#000000" alink="#000000">
|
||||
|
||||
<!--#include virtual="/CMake/HTML/Table.html"-->
|
||||
|
||||
<tr>
|
||||
<!--#include virtual="/CMake/HTML/SideBar.html"-->
|
||||
|
||||
<td width="600" valign="top" bgcolor="#FFFFFF">
|
||||
<div align="left">
|
||||
<font size=5>Welcome</font> to CMake, the cross-platform, open-source make
|
||||
system. CMake is used to control the software compilation process using
|
||||
simple platform and compiler independent configuration files. CMake
|
||||
generates native makefiles and workspaces that can be used in the compiler
|
||||
environment of your choice. CMake is quite sophisticated: it is possible to
|
||||
support complex environments requiring system configuration, pre-processor
|
||||
generation, code generation, and template instantiation. Please go <a
|
||||
href="/CMake/HTML/About.html">here</a> to learn more about CMake.
|
||||
|
||||
<P>
|
||||
CMake was developed by
|
||||
<a href="http://www.kitware.com">Kitware</a> as part of the
|
||||
<a href="http://public.kitware.com/Insight">NLM Insight Segmentation and
|
||||
Registration Toolkit</a> project.
|
||||
The <a href="http://www.asci.doe.gov/scs/views.htm">ASCI VIEWS project</a>
|
||||
also provided support in the context of their
|
||||
parallel computation environment. Other sponsors include the Insight,
|
||||
<a href="http://www.kitware.com/vtk.html">VTK</a>, and
|
||||
<a href="http://www.robots.ox.ac.uk/~vxl/">VXL</a>
|
||||
open source software communities.
|
||||
|
||||
<p>
|
||||
The goals for CMake include the following:
|
||||
<ul>
|
||||
<li>Develop an open source, cross-platform tool to manage the build process,
|
||||
<li>Allow the use of native compilers and systems,
|
||||
<li>Simplify the build process,
|
||||
<li>Optionally provide a user-interface to manage the build system,
|
||||
<li>Create an extensible framework,
|
||||
<li>Grow a self-sustaining community of software users and developers.
|
||||
</ul>
|
||||
<p><center>
|
||||
<a href="http://www.nlm.nih.gov">
|
||||
<img align=center src=Art/nlm_logo.gif border=0></a>
|
||||
|
||||
<a href="http://public.kitware.com/Insight">
|
||||
<img align=center src=Art/itkLogoSmallTransparentBackground.gif border=0></a>
|
||||
|
||||
<a href="http://www.kitware.com">
|
||||
<img align=center src=Art/swooshSmall.gif border=0></a>
|
||||
|
||||
<a href="http://www.acl.lanl.gov/">
|
||||
<img align=center src=Art/asci.gif border=0></a>
|
||||
|
||||
</center>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
Loading…
Reference in New Issue