4
The program depends on the CTN library developed by the
5
Mallinckrodt Institue of Radiology, Washington University in St. Louis
6
MO, http://wuerlim.wustl.edu/. The source code can be downloaded from
7
ftp://ftp.erl.wustl.edu/pub/dicom/software/ctn/
9
The program also depends on the nifticlib developed by the NIfTI
10
project, http://nifti.nimh.nih.gov/. The source code can be downloaded
11
from http://sourceforge.net/projects/niftilib.
16
The file `configure.in' is used to create `configure' by a program
17
called `autoconf'. You will need to run `autoconf' at least once to
18
generate the correct `configure' shell script.
20
The `configure' shell script attempts to guess correct values for
21
various system-dependent variables used during compilation. It uses
22
those values to create a `Makefile' in each directory of the package.
23
It may also create one or more `.h' files containing system-dependent
24
definitions. Finally, it creates a shell script `config.status' that
25
you can run in the future to recreate the current configuration, a file
26
`config.cache' that saves the results of its tests to speed up
27
reconfiguring, and a file `config.log' containing compiler output
28
(useful mainly for debugging `configure').
30
The simplest way to compile this package is:
32
1. `cd' to the program's top level directory and type
33
`autoconf'. You will need to do this only the first time you
34
build, or if you are building on different architectures.
36
2. Type `./configure' to configure the package for your system. If
37
you're using `csh' on an old version of System V, you might need
38
to type `sh ./configure' instead to prevent `csh' from trying to
39
execute `configure' itself.
41
Running `configure' takes awhile. While running, it prints some
42
messages telling which features it is checking for.
44
3. Type `make all' to compile the package.
46
4. Type `make install' to install the programs and any data files and
49
5. You can remove the program binaries and object files from the
50
source code directory by typing `make clean'.
55
By default, `make install' will install the package's files in
56
`/usr/local/bin', `/usr/local/man', etc. You can specify an
57
installation prefix other than `/usr/local' by giving `configure' the
58
option `--prefix=PATH'.
60
You can specify separate installation prefixes for
61
architecture-specific files and architecture-independent files. If you
62
give `configure' the option `--exec-prefix=PATH', the package will use
63
PATH as the prefix for installing programs and libraries.
64
Documentation and other data files will still use the regular prefix.
66
In addition, if you use an unusual directory layout you can give
67
options like `--bindir=PATH' to specify different values for particular
68
kinds of files. Run `configure --help' for a list of the directories
69
you can set and what kinds of files go in them.
added
removed
INSTALL
