Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Diff of /releases/install-latest.html [b2a8d6] .. [f130fc] Maximize Restore

  Switch to unified view

a/releases/install-latest.html b/releases/install-latest.html
1
1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2
<html>
2
<html>
3
  <head>
3
  <head>
4
    <title>Installing current VXL</title>
4
    <title>Installing latest VXL</title>
5
    <meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
6
    <style type="text/css">
7
      body { color: black ; background-color: white }
8
    </style>
5
  </head>
9
  </head>
6
10
7
  <body bgcolor=white>
11
<body>
8
<a href="http://vxl.sourceforge.net/" border=0><img ALT="VXL" src="../logo1-quant.gif" align=right border=0></a>
12
    <h1>Installing the latest version of <a href="http://vxl.sourceforge.net/"><img alt="VXL" src="../logo1-quant.gif" border="0" width="128" height="48"/></a></h1>
9
    <h1>Installing the latest version of VXL</h1>
10
<br clear=all>
11
<hr>
13
<hr/>
14
12
<b>Contents:</b>
15
<b>Contents:</b>
13
<a href="#cmake">[Installing CMake]</a>&nbsp;&nbsp;
16
<a href="#cmake">[Installing CMake]</a>&nbsp;&nbsp;
14
<a href="#compile">[Compiling with CMake]</a>&nbsp;&nbsp;
17
<a href="#compile">[Compiling with CMake]</a>&nbsp;&nbsp;
15
<a href="#cmakecache">[CMakeCache.txt]</a>&nbsp;&nbsp;
18
<a href="#cmakecache">[CMakeCache.txt]</a>&nbsp;&nbsp;
16
<a href="#in-place">[In-place builds]</a>&nbsp;&nbsp;
19
<a href="#in-place">[In-place builds]</a>&nbsp;&nbsp;
17
20
18
<hr>
21
<hr/>
19
<a name = "cmake">
22
20
<h1>Get and install CMake</h1></a> 
23
<h2><a name="cmake">Get and install CMake</a></h2>
21
24
22
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>.
25
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>.
23
VXL is designed to work with the latest release of CMake, as shown on the CMake website.
26
VXL is designed to work with the latest release of CMake, as shown on the CMake website.
24
27
25
<hr>
28
<hr/>
26
<a name = "compile">
29
27
<h3>Compiling with CMake</h3></a>
30
<h2><a name="compile">Compiling with CMake</a></h2>
28
31
29
<p>
32
<p>
30
Use $VXLSRC to refer to the vxl source tree. Create a different directory $VXLBIN, one per platform,
33
Use $VXLSRC to refer to the vxl source tree. Create a different directory $VXLBIN, one per platform,
31
and run CMake from within that directory.
34
and run CMake from within that directory.
32
</p>
35
</p>
33
36
34
<h2>With Visual Studio 6 and .NET</h2>
37
<h3>With Visual Studio 6 and .NET</h3>
35
38
36
<p>
39
<p>
37
Run CMakeSetup and enter $VXLSRC and $VXLBIN into the appropriate text
40
Run CMakeSetup and enter $VXLSRC and $VXLBIN into the appropriate text
38
fields. This will generate $VXLBIN/allvxl.dsw or $VXLBIN/allvxl.sln.
41
fields. This will generate $VXLBIN/allvxl.dsw or $VXLBIN/allvxl.sln.
39
All VXL projects are included in this workspace and you should be able
42
All VXL projects are included in this workspace and you should be able
40
to build them in the normal way for Visual Studio.
43
to build them in the normal way for Visual Studio.
41
</p>
44
</p>
42
45
43
<h4>With Unix (including Cygwin)</h4>
46
<h3>With Unix (including Cygwin)</h3>
44
<p>
47
45
<pre>
48
<pre>    cd $VXLBIN</pre>
46
  cd $VXLBIN
47
</pre>
48
and then
49
<pre>
50
  ccmake $VXLSRC      (Curses UI)
49
and then<pre>    ccmake $VXLSRC      (Curses UI)</pre>
51
</pre>
52
or
53
<pre>
54
  cmake -i $VXLSRC       (command line)
50
or<pre>    cmake -i $VXLSRC       (command line)</pre>
55
</pre>
51
56
52
57
<p>
53
<p>
58
This will generate the makefiles within $VXLBIN. You can now run
54
This will generate the makefiles within $VXLBIN. You can now run
59
"make" to build everything, or else go to a project of interest and
55
"make" to build everything, or else go to a project of interest and
60
run "make"--the dependent libraries should be automatically
56
run "make"--the dependent libraries should be automatically
61
built.
57
built.
62
</p>
58
</p>
63
59
60
<h4>Cygwin.</h4>
61
62
If you are using Cygwin and have installed the Cygwin OpenGL package,
63
you probably want to build with this option <pre>    cmake -i -DX11_INCLUDE_PATH:PATH=IGNORE $VXLSRC</pre>
64
64
<p>
65
<p>
65
<b>Cygwin.</b>
66
If you are using Cygwin and have installed the Cygwin OpenGL package,
67
you probably want to build with this option
68
<pre>
69
  cmake -i -DX11_INCLUDE_PATH:PATH=IGNORE $VXLSRC
70
</pre>
71
This prevents CMake from using the X11 headers and libraries.  The
66
This prevents CMake from using the X11 headers and libraries.  The
72
OpenGL package puts its header files in /usr/include/GL/ and the
67
OpenGL package puts its header files in /usr/include/GL/ and the
73
XFree86 package puts some header files in /usr/X11R6/include/GL/.  If
68
XFree86 package puts some header files in /usr/X11R6/include/GL/.  If
74
you configure to use header files from /usr/X11R6/include then the
69
you configure to use header files from /usr/X11R6/include then the
75
XFree86 GL/*.h files will be used instead of the OpenGL package GL/*.h
70
XFree86 GL/*.h files will be used instead of the OpenGL package GL/*.h
76
files.  These two sets of header files are not compatible.  Using the
71
files.  These two sets of header files are not compatible.  Using the
77
wrong ones will lead to linking problems involving mismatched suffixes
72
wrong ones will lead to linking problems involving mismatched suffixes
78
like @4, @8, and @12.
73
like @4, @8, and @12.
74
</p>
79
75
80
76
81
<hr>
77
<hr/>
82
<a name = "cmakecache">
78
83
<h2>The CMakeCache.txt</h2></a>
79
<h2><a name="cmakecache">The CMakeCache.txt</a></h2>
84
80
85
<p>
81
<p>
86
The build system is configured by setting "cache" values, which are
82
The build system is configured by setting "cache" values, which are
87
specified in $VXLBIN/CMakeCache.txt. These values can be edited using
83
specified in $VXLBIN/CMakeCache.txt. These values can be edited using
88
a plain old editor or using the CMake GUI.
84
a plain old editor or using the CMake GUI.
...
...
95
from a directory that already contains a CMakeCache.txt will use the
91
from a directory that already contains a CMakeCache.txt will use the
96
values in there, so it is worth having a look at the settings in that
92
values in there, so it is worth having a look at the settings in that
97
file, e.g. for the location of JPEG, TIFF, etc.
93
file, e.g. for the location of JPEG, TIFF, etc.
98
</p>
94
</p>
99
95
100
<hr>
96
<hr/>
101
<a name = "in-place">
97
102
<h2>Doing an in-place build</h2>
98
<h2><a name="in-place">Doing an in-place build</a></h2>
103
99
104
If you don't make a new directory for $VXLBIN, but instead use
100
If you don't make a new directory for $VXLBIN, but instead use
105
$VXLBIN=$VXLSRC, you will get an in-place build. The major
101
$VXLBIN=$VXLSRC, you will get an in-place build. The major
106
disadvantage is that you cannot have different build options, since
102
disadvantage is that you cannot have different build options, since
107
the build options are given in the CMakeCache.txt and there is only
103
the build options are given in the CMakeCache.txt and there is only
108
one of those per build tree.
104
one of those per build tree.
105
106
<hr/>
107
  <address>
108
   <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>
109
   <font color="blue">vxl-maintainers&nbsp;at&nbsp;lists&nbsp;dot&nbsp;sourceforge&nbsp;dot&nbsp;net</font>
110
  <br/>
111
   Hosted by <a href="http://sourceforge.net/"><img src="../sflogo.png" alt="SourceForge Logo" align="middle" border="0"/></a>
112
  </address>
113
114
  </body>
115
</html>