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
|
Copyright (C) 1997 Peter Kabal
The libtsp routines are provided free of charge without warranty of any kind.
All components are copyrighted. They may be distributed free of charge
provided that the recipients also acquire the right to distribute them. In no
case can this software be incorporated into a work which is distributed for a
fee.
Note: The Makefile files supplied as part of libtsp distribution are meant
for use with Gnu make. Many of them are unlikely to work with another make
program.
Building libtsp.a:
Unpack the sources. Denote the current directory as <LIBROOT>. Go into the
libtsp directory /libtsp).
- If you have GNU make, you can run make as follows
% make tspdir=<LIBROOT> -I<LIBROOT>/include
The tspdir variable can be used to redirect the library to be built
as $(tspdir)/lib/libtsp.a (using include files from directory
$(tspdir)/include). If unspecified, tspdir defaults to /usr/local.
- If you do not have GNU make, the script build_libtsp will build the
library as <LIBROOT>/lib/libtsp.a.
Using the library routines:
To use the libtsp routines in a program you will have to link with the
object library libtsp.a. Furthermore, user programs need access to the
header file libtsp.h. I suggest putting libtsp.a (or a link to it) in
/usr/local/lib and libtsp.h (or a link to it) in /usr/local/include.
Man page files:
The directory man contains man pages for the top level libtsp routines.
These man pages have been automatically generated from the corresponding
file header and so contain the same information as the file header itself.
The extensions for the man pages are .3tsp. On some systems, these will have
to be renamed to have an extension of .3 in order for the man program to
recognize them.
html files:
The directory html contains html files for top level libtsp routines. These
html pages have been automatically generated from the corresponding file
header and so contain the same information as the file header itself.
Test programs:
Below each of the subdirectories of libtsp is a test directory containing
test programs that exercise the libtsp routines. Makefile's (for Gnu make)
in those directories will build the test programs and compare the output
with a reference output.
Other files:
A number of routines are hidden one level down in a "nucleus" directory.
These are internal routines usually not of interest to the end user.
A number of audio files of various formats can be found in the
libtsp/AF/test/audiofiles directory.
The header files in the include/libtsp directory are used to define internal
data structures. While not usually used directly by the end user, these
header files should be available, particularly for rebuilding the library.
These might find a home in the directory /usr/local/include/libtsp.
Systems:
The libtsp routines have been built on the systems listed below. Extensive
testing has been carried out for only the first four configurations listed.
- SunOS 4.1 running on a Sparc machine (cc, acc, CC and gcc compilers)
- Irix 5.2 running on a SGI Indy (cc and gcc compilers)
- DEC Ultrix 4.x running on a DECstation (mips cc and gcc compilers)
- SunOS 5.5 (Solaris) running on a Sparc machine (cc and gcc compilers)
- OSF/1 V1.3 running on a DEC 3000 Model 300LX (cc compiler)
- HPUX 9.01 running on a HP 735 (cc and gcc compilers)
- MS-DOS running on a PC-386/486 (MS Visual C++ and djgpp gcc compilers)
For MSVC: use /Za and the Large memory model as compiler options; stack
size 34000, 256 segments, and /NOE as linker options.
$Id: INSTALL,v 1.8 1997/03/09 libtsp-V2R8 $
|
