/[public]/psiconv/trunk/INSTALL

Diff of /psiconv/trunk/INSTALL

Parent Directory | Revision Log | View Patch Patch

Revision 2		Revision 147
1	PREFACE	1	Copyright 1994, 1995, 1996, 1999, 2000, 2001 Free Software Foundation,
2	=======	2	Inc.
3		3
4	As of version 0.5, the psiconv package uses automake, autoconf and libtool.	4	This file is free documentation; the Free Software Foundation gives
5	This should make it possible to compile it on almost any architecture.	5	unlimited permission to copy, distribute and modify it.
6	Of course, this all depends on whether I have isolated all possible
7	incompatibilities. If it does not compile for you, please send me a
8	bug report, with as much information as possible, or even patches if
9	you know what causes the problems.
10
11	If your platform has no 32-bit integers (as int, long or long long), you
12	can forget about compiling libpsiconv. Sorry.
13
14	There is no manpage yet for psiconv, but try `psiconv -h' for some help.
15
16	The included format data text files are translated by `make all' from
17	Psion Word to HTML. This process should succeed with no warnings or
18	errors. If the translation is ended without problems, psiconv is probably
19	working right.
20
21		6
22	Basic Installation	7	Basic Installation
23	==================	8	==================
24		9
25	These are generic installation instructions.	10	These are generic installation instructions.
…		…
27	The `configure' shell script attempts to guess correct values for	12	The `configure' shell script attempts to guess correct values for
28	various system-dependent variables used during compilation. It uses	13	various system-dependent variables used during compilation. It uses
29	those values to create a `Makefile' in each directory of the package.	14	those values to create a `Makefile' in each directory of the package.
30	It may also create one or more `.h' files containing system-dependent	15	It may also create one or more `.h' files containing system-dependent
31	definitions. Finally, it creates a shell script `config.status' that	16	definitions. Finally, it creates a shell script `config.status' that
32	you can run in the future to recreate the current configuration, a file	17	you can run in the future to recreate the current configuration, and a
33	`config.cache' that saves the results of its tests to speed up	18	file `config.log' containing compiler output (useful mainly for
34	reconfiguring, and a file `config.log' containing compiler output	19	debugging `configure').
35	(useful mainly for debugging `configure').	20
		21	It can also use an optional file (typically called `config.cache'
		22	and enabled with `--cache-file=config.cache' or simply `-C') that saves
		23	the results of its tests to speed up reconfiguring. (Caching is
		24	disabled by default to prevent problems with accidental use of stale
		25	cache files.)
36		26
37	If you need to do unusual things to compile the package, please try	27	If you need to do unusual things to compile the package, please try
38	to figure out how `configure' could check whether to do them, and mail	28	to figure out how `configure' could check whether to do them, and mail
39	diffs or instructions to the address given in the `README' so they can	29	diffs or instructions to the address given in the `README' so they can
40	be considered for the next release. If at some point `config.cache'	30	be considered for the next release. If you are using the cache, and at
41	contains results you don't want to keep, you may remove or edit it.	31	some point `config.cache' contains results you don't want to keep, you
		32	may remove or edit it.
42		33
43	The file `configure.in' is used to create `configure' by a program	34	The file `configure.ac' (or `configure.in') is used to create
44	called `autoconf'. You only need `configure.in' if you want to change	35	`configure' by a program called `autoconf'. You only need
45	it or regenerate `configure' using a newer version of `autoconf'.	36	`configure.ac' if you want to change it or regenerate `configure' using
		37	a newer version of `autoconf'.
46		38
47	The simplest way to compile this package is:	39	The simplest way to compile this package is:
48		40
49	1. `cd' to the directory containing the package's source code and type	41	1. `cd' to the directory containing the package's source code and type
50	`./configure' to configure the package for your system. If you're	42	`./configure' to configure the package for your system. If you're
…		…
74		66
75	Compilers and Options	67	Compilers and Options
76	=====================	68	=====================
77		69
78	Some systems require unusual options for compilation or linking that	70	Some systems require unusual options for compilation or linking that
79	the `configure' script does not know about. You can give `configure'	71	the `configure' script does not know about. Run `./configure --help'
80	initial values for variables by setting them in the environment. Using	72	for details on some of the pertinent environment variables.
81	a Bourne-compatible shell, you can do that on the command line like
82	this:
83	CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
84		73
85	Or on systems that have the `env' program, you can do it like this:	74	You can give `configure' initial values for variables by setting
86	env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure	75	them in the environment. You can do that on the command line like this:
		76
		77	./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
		78
		79	*Note Defining Variables::, for more details.
87		80
88	Compiling For Multiple Architectures	81	Compiling For Multiple Architectures
89	====================================	82	====================================
90		83
91	You can compile the package for more than one kind of computer at the	84	You can compile the package for more than one kind of computer at the
…		…
94	supports the `VPATH' variable, such as GNU `make'. `cd' to the	87	supports the `VPATH' variable, such as GNU `make'. `cd' to the
95	directory where you want the object files and executables to go and run	88	directory where you want the object files and executables to go and run
96	the `configure' script. `configure' automatically checks for the	89	the `configure' script. `configure' automatically checks for the
97	source code in the directory that `configure' is in and in `..'.	90	source code in the directory that `configure' is in and in `..'.
98		91
99	If you have to use a `make' that does not supports the `VPATH'	92	If you have to use a `make' that does not support the `VPATH'
100	variable, you have to compile the package for one architecture at a time	93	variable, you have to compile the package for one architecture at a
101	in the source code directory. After you have installed the package for	94	time in the source code directory. After you have installed the
102	one architecture, use `make distclean' before reconfiguring for another	95	package for one architecture, use `make distclean' before reconfiguring
103	architecture.	96	for another architecture.
104		97
105	Installation Names	98	Installation Names
106	==================	99	==================
107		100
108	By default, `make install' will install the package's files in	101	By default, `make install' will install the package's files in
…		…
141	`--x-libraries=DIR' to specify their locations.	134	`--x-libraries=DIR' to specify their locations.
142		135
143	Specifying the System Type	136	Specifying the System Type
144	==========================	137	==========================
145		138
146	There may be some features `configure' can not figure out	139	There may be some features `configure' cannot figure out
147	automatically, but needs to determine by the type of host the package	140	automatically, but needs to determine by the type of host the package
148	will run on. Usually `configure' can figure that out, but if it prints	141	will run on. Usually `configure' can figure that out, but if it prints
149	a message saying it can not guess the host type, give it the	142	a message saying it cannot guess the host type, give it the
150	`--host=TYPE' option. TYPE can either be a short name for the system	143	`--build=TYPE' option. TYPE can either be a short name for the system
151	type, such as `sun4', or a canonical name with three fields:	144	type, such as `sun4', or a canonical name which has the form:
		145
152	CPU-COMPANY-SYSTEM	146	CPU-COMPANY-SYSTEM
153		147
		148	where SYSTEM can have one of these forms:
		149
		150	OS KERNEL-OS
		151
154	See the file `config.sub' for the possible values of each field. If	152	See the file `config.sub' for the possible values of each field. If
155	`config.sub' isn't included in this package, then this package doesn't	153	`config.sub' isn't included in this package, then this package doesn't
156	need to know the host type.	154	need to know the host type.
157		155
158	If you are building compiler tools for cross-compiling, you can also	156	If you are _building_ compiler tools for cross-compiling, you should
159	use the `--target=TYPE' option to select the type of system they will	157	use the `--target=TYPE' option to select the type of system they will
160	produce code for and the `--build=TYPE' option to select the type of	158	produce code for.
161	system on which you are compiling the package.	159
		160	If you want to _use_ a cross compiler, that generates code for a
		161	platform different from the build platform, you should specify the host
		162	platform (i.e., that on which the generated programs will eventually be
		163	run) with `--host=TYPE'. In this case, you should also specify the
		164	build platform with `--build=TYPE', because, in this case, it may not
		165	be possible to guess the build platform (it sometimes involves
		166	compiling and running simple test programs, and this can't be done if
		167	the compiler is a cross compiler).
162		168
163	Sharing Defaults	169	Sharing Defaults
164	================	170	================
165		171
166	If you want to set default values for `configure' scripts to share,	172	If you want to set default values for `configure' scripts to share,
…		…
169	`configure' looks for `PREFIX/share/config.site' if it exists, then	175	`configure' looks for `PREFIX/share/config.site' if it exists, then
170	`PREFIX/etc/config.site' if it exists. Or, you can set the	176	`PREFIX/etc/config.site' if it exists. Or, you can set the
171	`CONFIG_SITE' environment variable to the location of the site script.	177	`CONFIG_SITE' environment variable to the location of the site script.
172	A warning: not all `configure' scripts look for a site script.	178	A warning: not all `configure' scripts look for a site script.
173		179
174	Operation Controls	180	Defining Variables
175	==================	181	==================
		182
		183	Variables not defined in a site shell script can be set in the
		184	environment passed to `configure'. However, some packages may run
		185	configure again during the build, and the customized values of these
		186	variables may be lost. In order to avoid this problem, you should set
		187	them in the `configure' command line, using `VAR=value'. For example:
		188
		189	./configure CC=/usr/local2/bin/gcc
		190
		191	will cause the specified gcc to be used as the C compiler (unless it is
		192	overridden in the site shell script).
		193
		194	`configure' Invocation
		195	======================
176		196
177	`configure' recognizes the following options to control how it	197	`configure' recognizes the following options to control how it
178	operates.	198	operates.
179		199
		200	`--help'
		201	`-h'
		202	Print a summary of the options to `configure', and exit.
		203
		204	`--version'
		205	`-V'
		206	Print the version of Autoconf used to generate the `configure'
		207	script, and exit.
		208
180	`--cache-file=FILE'	209	`--cache-file=FILE'
181	Use and save the results of the tests in FILE instead of	210	Enable the cache: use and save the results of the tests in FILE,
182	`./config.cache'. Set FILE to `/dev/null' to disable caching, for	211	traditionally `config.cache'. FILE defaults to `/dev/null' to
183	debugging `configure'.	212	disable caching.
184		213
185	`--help'	214	`--config-cache'
186	Print a summary of the options to `configure', and exit.	215	`-C'
		216	Alias for `--cache-file=config.cache'.
187		217
188	`--quiet'	218	`--quiet'
189	`--silent'	219	`--silent'
190	`-q'	220	`-q'
191	Do not print messages saying which checks are being made. To	221	Do not print messages saying which checks are being made. To
…		…
194		224
195	`--srcdir=DIR'	225	`--srcdir=DIR'
196	Look for the package's source code in directory DIR. Usually	226	Look for the package's source code in directory DIR. Usually
197	`configure' can determine that directory automatically.	227	`configure' can determine that directory automatically.
198		228
199	`--version'
200	Print the version of Autoconf used to generate the `configure'
201	script, and exit.
202
203	`configure' also accepts some other, not widely useful, options.	229	`configure' also accepts some other, not widely useful, options. Run
		230	`configure --help' for more details.
		231

 Legend:



Removed from v.2
 


changed lines


 
Added in v.147
 Legend:



Removed from v.2
 


changed lines


 
Added in v.147
-Removed from v.2
+Added in v.147

frodo@frodo.looijaard.name	ViewVC Help
Powered by ViewVC 1.1.26