Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

[020868]: INSTALL.html Maximize Restore History

Download this file

INSTALL.html    109 lines (91 with data), 3.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
<html>
<head>
<title>Installing current VXL</title>
</head>
<body bgcolor=white>
<a href="http://vxl.sourceforge.net/" border=0><img ALT="VXL" src="../logo1-quant.gif" align=right border=0></a>
<h1>Installing the latest version of VXL</h1>
<br clear=all>
<hr>
<b>Contents:</b>
<a href="#cmake">[Installing CMake]</a>&nbsp;&nbsp;
<a href="#compile">[Compiling with CMake]</a>&nbsp;&nbsp;
<a href="#cmakecache">[CMakeCache.txt]</a>&nbsp;&nbsp;
<a href="#in-place">[In-place builds]</a>&nbsp;&nbsp;
<hr>
<a name = "cmake">
<h1>Get and install CMake</h1></a>
If you haven't already downloaded CMake then you will first need to get this first from the <a href="http://www.cmake.org/">CMake website</a>.
VXL is designed to work with the latest release of CMake, as shown on the CMake website.
<hr>
<a name = "compile">
<h3>Compiling with CMake</h3></a>
<p>
Use $VXLSRC to refer to the vxl source tree. Create a different directory $VXLBIN, one per platform,
and run CMake from within that directory.
</p>
<h2>With Visual Studio 6 and .NET</h2>
<p>
Run CMakeSetup and enter $VXLSRC and $VXLBIN into the appropriate text
fields. This will generate $VXLBIN/allvxl.dsw or $VXLBIN/allvxl.sln.
All VXL projects are included in this workspace and you should be able
to build them in the normal way for Visual Studio.
</p>
<h4>With Unix (including Cygwin)</h4>
<p>
<pre>
cd $VXLBIN
</pre>
and then
<pre>
ccmake $VXLSRC (Curses UI)
</pre>
or
<pre>
cmake -i $VXLSRC (command line)
</pre>
<p>
This will generate the makefiles within $VXLBIN. You can now run
"make" to build everything, or else go to a project of interest and
run "make"--the dependent libraries should be automatically
built.
</p>
<p>
<b>Cygwin.</b>
If you are using Cygwin and have installed the Cygwin OpenGL package,
you probably want to build with this option
<pre>
cmake -i -DX11_INCLUDE_PATH:PATH=IGNORE $VXLSRC
</pre>
This prevents CMake from using the X11 headers and libraries. The
OpenGL package puts its header files in /usr/include/GL/ and the
XFree86 package puts some header files in /usr/X11R6/include/GL/. If
you configure to use header files from /usr/X11R6/include then the
XFree86 GL/*.h files will be used instead of the OpenGL package GL/*.h
files. These two sets of header files are not compatible. Using the
wrong ones will lead to linking problems involving mismatched suffixes
like @4, @8, and @12.
<hr>
<a name = "cmakecache">
<h2>The CMakeCache.txt</h2></a>
<p>
The build system is configured by setting "cache" values, which are
specified in $VXLBIN/CMakeCache.txt. These values can be edited using
a plain old editor or using the CMake GUI.
</p>
<p>
When running CMake for the first time, sensible default values are
written into CMakeCache.txt, and you will not need to change any of
these if everything compiles and runs fine. However, running CMake
from a directory that already contains a CMakeCache.txt will use the
values in there, so it is worth having a look at the settings in that
file, e.g. for the location of JPEG, TIFF, etc.
</p>
<hr>
<a name = "in-place">
<h2>Doing an in-place build</h2>
If you don't make a new directory for $VXLBIN, but instead use
$VXLBIN=$VXLSRC, you will get an in-place build. The major
disadvantage is that you cannot have different build options, since
the build options are given in the CMakeCache.txt and there is only
one of those per build tree.