1 TINA6 SPECIFIC INSTRUCTIONS
5 TINA6 provides a set of libraries for machine vision and medical image
6 analysis research. The libraries are distributed as two directories:
7 tina-libs for the backend code (memory management, file I/O, data
8 structures etc) and tina-tools for the front end and algorithmic
11 Tarballs of the tina-libs and tina-tools code can be obtained from the
12 TINA website (http://www.tina-vision.net/tarballs/). Download both
13 tarballs e.g.
18 The build number (xxx) should be the same for both tarballs in order to
19 ensure compatibility. Place both tarballs into a directory (e.g.
20 /usr/local), then unzip and untar them. To compile the libraries, first
21 cd into the tina-libs-6.0rcbuildxxx directory and type:
25 make install
27 Then repeat in the tina-tools-6.0rcbuildxxx directory.
29 The libraries can be used in one of two ways: either to provide
30 functionality for your own code, or by building a "toolkit", which
31 provides a graphical interface to some or all of the algorithms in the
32 libraries. Most TINA users will eventually want to build their own
33 toolkits, including only the algorithms needed for specific research
34 projects. However, several examples have been included in the tina-tools
35 area, as directories under "toolkits". To build one, cd into the
36 directory and type "make". This will produce the "tinaTool" executable,
37 which can be run from a terminal.
39 For further details, see the README file, or the www.tina-vision.net
42 firstname.lastname@example.org 04/11/2009
45 GENERIC INSTRUCTIONS
49 Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
50 Foundation, Inc.
52 This file is free documentation; the Free Software Foundation gives
53 unlimited permission to copy, distribute and modify it.
55 Basic Installation
58 These are generic installation instructions.
60 The `configure' shell script attempts to guess correct values for
61 various system-dependent variables used during compilation. It uses
62 those values to create a `Makefile' in each directory of the package.
63 It may also create one or more `.h' files containing system-dependent
64 definitions. Finally, it creates a shell script `config.status' that
65 you can run in the future to recreate the current configuration, a file
66 `config.cache' that saves the results of its tests to speed up
67 reconfiguring, and a file `config.log' containing compiler output
68 (useful mainly for debugging `configure').
70 If you need to do unusual things to compile the package, please try
71 to figure out how `configure' could check whether to do them, and mail
72 diffs or instructions to the address given in the `README' so they can
73 be considered for the next release. If at some point `config.cache'
74 contains results you don't want to keep, you may remove or edit it.
76 The file `configure.in' is used to create `configure' by a program
77 called `autoconf'. You only need `configure.in' if you want to change
78 it or regenerate `configure' using a newer version of `autoconf'.
80 The simplest way to compile this package is:
82 1. `cd' to the directory containing the package's source code and type
83 `./configure' to configure the package for your system. If you're
84 using `csh' on an old version of System V, you might need to type
85 `sh ./configure' instead to prevent `csh' from trying to execute
86 `configure' itself.
88 Running `configure' takes awhile. While running, it prints some
89 messages telling which features it is checking for.
91 2. Type `make' to compile the package.
93 3. Optionally, type `make check' to run any self-tests that come with
94 the package.
96 4. Type `make install' to install the programs and any data files and
99 5. You can remove the program binaries and object files from the
100 source code directory by typing `make clean'. To also remove the
101 files that `configure' created (so you can compile the package for
102 a different kind of computer), type `make distclean'. There is
103 also a `make maintainer-clean' target, but that is intended mainly
104 for the package's developers. If you use it, you may have to get
105 all sorts of other programs in order to regenerate files that came
106 with the distribution.
108 Compilers and Options
111 Some systems require unusual options for compilation or linking that
112 the `configure' script does not know about. You can give `configure'
113 initial values for variables by setting them in the environment. Using
114 a Bourne-compatible shell, you can do that on the command line like
116 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
118 Or on systems that have the `env' program, you can do it like this:
119 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
121 Compiling For Multiple Architectures
124 You can compile the package for more than one kind of computer at the
125 same time, by placing the object files for each architecture in their
126 own directory. To do this, you must use a version of `make' that
127 supports the `VPATH' variable, such as GNU `make'. `cd' to the
128 directory where you want the object files and executables to go and run
129 the `configure' script. `configure' automatically checks for the
130 source code in the directory that `configure' is in and in `..'.
132 If you have to use a `make' that does not supports the `VPATH'
133 variable, you have to compile the package for one architecture at a time
134 in the source code directory. After you have installed the package for
135 one architecture, use `make distclean' before reconfiguring for another
138 Installation Names
141 By default, `make install' will install the package's files in
142 `/usr/local/bin', `/usr/local/man', etc. You can specify an
143 installation prefix other than `/usr/local' by giving `configure' the
144 option `--prefix=PATH'.
146 You can specify separate installation prefixes for
147 architecture-specific files and architecture-independent files. If you
148 give `configure' the option `--exec-prefix=PATH', the package will use
149 PATH as the prefix for installing programs and libraries.
150 Documentation and other data files will still use the regular prefix.
152 In addition, if you use an unusual directory layout you can give
153 options like `--bindir=PATH' to specify different values for particular
154 kinds of files. Run `configure --help' for a list of the directories
155 you can set and what kinds of files go in them.
157 If the package supports it, you can cause programs to be installed
158 with an extra prefix or suffix on their names by giving `configure' the
159 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
161 Optional Features
164 Some packages pay attention to `--enable-FEATURE' options to
165 `configure', where FEATURE indicates an optional part of the package.
166 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
167 is something like `gnu-as' or `x' (for the X Window System). The
168 `README' should mention any `--enable-' and `--with-' options that the
169 package recognizes.
171 For packages that use the X Window System, `configure' can usually
172 find the X include and library files automatically, but if it doesn't,
173 you can use the `configure' options `--x-includes=DIR' and
174 `--x-libraries=DIR' to specify their locations.
176 Specifying the System Type
179 There may be some features `configure' can not figure out
180 automatically, but needs to determine by the type of host the package
181 will run on. Usually `configure' can figure that out, but if it prints
182 a message saying it can not guess the host type, give it the
183 `--host=TYPE' option. TYPE can either be a short name for the system
184 type, such as `sun4', or a canonical name with three fields:
187 See the file `config.sub' for the possible values of each field. If
188 `config.sub' isn't included in this package, then this package doesn't
189 need to know the host type.
191 If you are building compiler tools for cross-compiling, you can also
192 use the `--target=TYPE' option to select the type of system they will
193 produce code for and the `--build=TYPE' option to select the type of
194 system on which you are compiling the package.
196 Sharing Defaults
199 If you want to set default values for `configure' scripts to share,
200 you can create a site shell script called `config.site' that gives
201 default values for variables like `CC', `cache_file', and `prefix'.
202 `configure' looks for `PREFIX/share/config.site' if it exists, then
203 `PREFIX/etc/config.site' if it exists. Or, you can set the
204 `CONFIG_SITE' environment variable to the location of the site script.
205 A warning: not all `configure' scripts look for a site script.
207 Operation Controls
210 `configure' recognizes the following options to control how it
214 Use and save the results of the tests in FILE instead of
215 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
216 debugging `configure'.
219 Print a summary of the options to `configure', and exit.
224 Do not print messages saying which checks are being made. To
225 suppress all normal output, redirect it to `/dev/null' (any error
226 messages will still be shown).
229 Look for the package's source code in directory DIR. Usually
230 `configure' can determine that directory automatically.
233 Print the version of Autoconf used to generate the `configure'
234 script, and exit.
236 `configure' also accepts some other, not widely useful, options.
This page was automatically generated by the
Visit the LXR main site for more