[347d75]: releases / install-release.html Maximize Restore History

Download this file

install-release.html    220 lines (191 with data), 8.4 kB

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Install VXL 1.7 release</title>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<style type="text/css">
body { color: black ; background-color: white }
</style>
</head>
<body>
<h1>Installing the <a href="http://vxl.sourceforge.net/"><img alt="VXL" src="../logo1-quant.gif" border="0" width="128" height="48"/></a> 1.7 release</h1>
<hr/>
<h2><a name="unix-build">Configuration</a></h2>
<p>
The most common build system used for VXL is <a href="http://www.cmake.org/">CMake</a>.
You should first download and install CMake. VXL requires CMake version 2.2 or higher.
</p>
<p>
Extract the VXL source into the directory <b>vxl-1.7</b>. Create a
separate output directory <b>bin</b> parallel to the source directory:
</p>
<pre>
.../.../... ---+--- vxl-1.7 ---+--- vxl
| |
| +--- vcl
| ...
|
+--- bin
</pre>
<p>
Let us call the former <code>$VXLSRC</code> and the latter <code>$VXLBIN</code>.
</p>
<p>
Change current directory to <code>$VXLBIN</code> and run CMake, specifying <code>$VXLSRC</code>
as the source directory.
</p>
<dl>
<dt><b>Unix and Cygwin:</b></dt>
<dd>Run the Curses based front-end
<pre>
ccmake $VXLSRC
</pre>
or the command line front-end
<pre>
cmake -i $VXLSRC
</pre>
</dd>
<dt><b>Windows:</b></dt>
<dd>Run CMakeSetup and specify the source and binary directories as <code>$VXLSRC</code> and
<code>$VXLBIN</code>, respectively. In the box on the upper right, choose the build system you use.
</dd>
</dl>
<p>
Repeatedly select "Configure" ("C" on Unix) until the entries stop
changing and you get the chance to generate the makefiles ("OK" on
Windows, and "G" on Unix).
<br/>
You may ignore any "something-NOTFOUND" message since these refer to optional components.
But if you are sure that one of these components is present on your system, manually fill in the correct path and re-run configure.
</p>
<p>
In the CMake interface, you can choose which parts of the VXL tree to
build. The default is to build everything except vgui and its
dependents. Building vgui requires the presence of OpenGL and
GLU. Often, these are in a platform specific area of the machine, and
hence cannot be detected by CMake. If you have these on your system,
and wish to build vgui, set BUILD_VGUI to "ON" and make sure the
appropriate entries in the CMake cache are valid. With Windows, the
required libraries (MFC and OpenGL) are shipped with the operating
system, so you should be able to build vgui without any issues.
</p>
<h2>Build</h2>
<p>
Now you can build the libraries.
</p>
<dl>
<dt><b>Unix or Cygwin:</b></dt>
<dd>Run make
<pre>
make
</pre>
</dd>
<dt><b>Windows and MSVC:</b></dt>
<dd>Build VXL by loading the <code>$VXLBIN\vxl.dsw</code> into Developer Studio and
building the ALL_BUILD target. This project is a little larger than Developer
Studio can sometimes cope with, so you can do a full build from the command line:
<pre>
vcvars32.bat
msdev vxl.dsw /MAKE "ALL_BUILD - Win32 Debug"
</pre>
Or the speedier release version
<pre>
msdev vxl.dsw /MAKE "ALL_BUILD - Win32 Release"
</pre>
</dd>
<dt><b>Windows and Visual Studio 7 and above:</b></dt>
<dd>Build VXL by loading the <code>$VXLBIN\vxl.sln</code> into Developer Studio and
building the ALL_BUILD target.
</dd>
</dl>
<h2>Test</h2>
<p>
You can run the test suite using the <code>ctest</code> program that came with CMake
</p>
<hr/>
<h2><a name="docs">Documentation</a></h2>
<h3>Documentation on the whole of VXL</h3>
<p>
There are two main references for information on the whole of VXL:
</p>
<ul>
<li><a href="http://paine.wiau.man.ac.uk/pub/doc_vxl/index.html">VXL package documentation</a>
- this documents the latest snapshot of VXL.
It includes auto-generated descriptions of every
class and function in VXL.</li>
<li><a href="http://paine.wiau.man.ac.uk/pub/doc_vxl/books/core/book.html">VXL book</a>
- this is a single reference for all high-level documentation on VXL. It currently documents
the CVS snapshot of VXL.</li>
</ul>
<p>
The <a href="http://www.isbe.man.ac.uk/search_vxl.html">documentation search</a>
page is useful for quickly finding documentation. You can also <a href="http://paine.wiau.man.ac.uk/pub/doc_vxl/doc_vxl.tar.gz"> download</a> the
entire snapshot documentation.
</p>
<h3>VXL guides</h3>
<p>
These are short guides to specific areas in VXL:
</p>
<ul>
<li><b>xcv</b> is an application built to demonstrate the functionality of the VXL libraries.
<ul>
<li>There is a <a href="http://vxl.cvs.sourceforge.net/vxl/www/manuals/xcv/newxcv.html">guide to using xcv</a>
(also available <a href="http://vxl.cvs.sourceforge.net/vxl/www/manuals/xcv.ps.gz">in postscript format</a>).</li>
<li>Download <a href="http://vxl.cvs.sourceforge.net/vxl/www/manuals/xcv.zip">xcv for Windows</a>,
<a href="http://vxl.cvs.sourceforge.net/vxl/www/manuals/xcv-SunOS5.bin.gz">xcv for solaris</a>.
and <a href="http://vxl.cvs.sourceforge.net/vxl/www/manuals/xcv-linux.bin.gz">xcv for linux</a></li>
<li>Here is some <a href ="http://vxl.cvs.sourceforge.net/vxl/www/manuals/xcvdata.tar.gz">example data</a>
suitable for use with xcv.</li>
</ul>
<br/>
</li>
<li><b>vgui</b> is the VXL graphical user interface library.
<ul>
<li>For a simple introduction to using VGUI there is the
<a href="http://vxl.cvs.sourceforge.net/vxl/www/manuals/vgui_users_guide/index.html">VGUI users guide</a>
(also <a href="http://vxl.cvs.sourceforge.net/vxl/www/manuals/vgui_users_guide.ps.gz">in postscript format</a>).
Here is the <a href ="http://vxl.cvs.sourceforge.net/vxl/www/manuals/examples-tutorial.tar.gz">
example code</a> used in the guide.</li>
<li>The <a href="http://vxl.cvs.sourceforge.net/vxl/www/manuals/vgui_ref_manual/index.html">VGUI
reference manual</a> (also <a href="http://vxl.cvs.sourceforge.net/vxl/www/manuals/vgui_ref_manual.ps.gz">in
postscript format</a>) is designed for developers of VGUI.</li>
</ul>
</li>
</ul>
<p>
xcv and vgui have not changed a lot since the last release of VXL so these guides should be useful for both
the release and development versions of VXL.
</p>
<ul>
<li>The <a href="http://paine.wiau.man.ac.uk/pub/doc_vxl/books/contrib/mul/book.html">MUL book</a> is an overview of libraries concerned with probability modelling, classification, and 3d and registered images.</li>
</ul>
<hr/>
<h2>Problems and where to get help</h2>
<p>
Have a look through the <a href="http://vxl.sourceforge.net/build-faq.html">Build FAQ</a>.
</p>
<p>
If you think you have found a bug, or if you have an installation or build problem, please submit a bug
report on the <a href="http://lists.sourceforge.net/lists/listinfo/vxl-users">vxl-users
mailing list</a>. Also supply the following information unless you know for certain it is not relevant:
</p>
<ul>
<li> Exactly what you did and exactly what goes wrong. Be verbose. We need to know this in order to help.
If you have problems configuring VXL, include the options you gave to configure and the output it
produced. If you have problems compiling VXL, include the command the makefiles issued, as well as
the entire error message. </li>
<li> Compiler and <i>compiler version number</i>. For gcc, this means we want the output of the
two shell commands &quot;<code>gcc -v</code>&quot; and &quot;<code>g++ -v</code>&quot;
(yes, both, please - they have been known to differ). For other
compilers try <code>-V</code>, <code>-ver</code>, <code>--version</code> or read the manual. </li>
<li> Operating system (e.g. linux/solaris/irix) and architecture (e.g. i386/sparc/mips). </li>
</ul>
<hr/>
<address>
<a href="http://validator.w3.org/check?uri=referer"><img src="../valid-html401.png" height="31" width="88" align="right" border="0" alt="Valid HTML 4.01 Transitional"/></a>
<font color="blue">vxl-maintainers&nbsp;at&nbsp;lists&nbsp;dot&nbsp;sourceforge&nbsp;dot&nbsp;net</font>
<br/>
Hosted by <a href="http://sourceforge.net/"><img src="../sflogo.png" alt="SourceForge Logo" align="middle" border="0"/></a>
</address>
</body>
</html>