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
|
Installation Procedure for Ytalk
0) Preparation
To build and install Ytalk, you need to unpack the archive. Since you're
reading this text, you have presumabley already done that. Ytalk uses
GNU autoconf now for configuration; those of you familiar with compiling
GNU utilities will feel quite at home.
Short & sweet:
./configure
make
make install
1) Configuration
To configure Ytalk, run the `configure' script provided with the
distribution. You may use all the standard arguments configure scripts
take. The most important ones are:
--help print help message
--prefix=PREFIX install architecture-independent files in PREFIX
(/usr/local by default)
--bindir=DIR user executables in DIR (PREFIX/bin)
--mandir=DIR man documentation in DIR [PREFIX/man]
--with-curses=DIR specify where to find curses
--enable-debug compile in memory tracking and debug messages
The `./configure' script also understands a number of environment variables:
CPPFLAGS flags to give to CPP and CC.
ex: CPPFLAGS=-I/path/to/some/include/dir ./configure
LIBS extra libraries to link to, and/or where to find them.
ex: LIBS="-L/path/to/extra/libs -R/path/to/extra/libs" ./configure
CFLAGS flags to give when compiling (default is -g -O2).
ex: CFLAGS=-O2 ./configure
LDFLAGS extra flags to give when linking.
ex: LDFLAGS=-s ./configure
You can customize many default settings by editing Makefile and
config.h. The program will work very well without your touching these
files, but it is useful to have a look at things you can change there.
2) Compilation
To compile the program, type make and cross your fingers. YTalk is
fairly portable, so this _should_ work out of the box. If it doesn't,
please mail me with all the details at <keso@impul.se>.
After the compilation, a ready to use `ytalk' executable should reside
in the distribution directory. Other than missing its system-wide
configuration file, it'll be all ready to use.
This is also the right moment to look at the file `ytalkrc', which will
be installed as the system-wide configuration file.
If you change any options in the Makefile, please run "make clean"
before recompiling. If you change the environment variables to run
`./configure' again, please delete the file `config.cache'.
3) Installation
Use `make install' to install Ytalk to the directories specified to
configure (/usr/local/* by default).
The standard installation process will copy the ytalk binary to
/usr/local/bin, the man page to /usr/local/man/man1, and the system
ytalkrc to /usr/local/etc. You can customize the directories either
through the configuration process or making the necessary changes in the
Makefile.
To delete the files created by Ytalk installation, you can use make
uninstall.
4) Acknowledgements (Roger Espel Llima)
Previous YTalk versions were maintained by Britt Yenne; since version
3.0pl2 was released quite a few years ago, I assume he has lost interest
in Ytalk, so I've been maintaining it in a "low-key" way (mostly just
fixing bugs and adding minor things, now autoconf-ing it, and
integrating people's bug fixes).
Most of these installation instructions are taken word-for-word from the
`INSTALL' file that comes with GNU Wget. This means that, unlike the
rest of the YTalk package (which is freely copyable as long as the
copyright notices are kept in the sources), this file is (probably)
covered by the GNU General Public License version 2.
|
