| 1 | PREFACE |
1 | Installation Instructions |
| 2 | ======= |
2 | ************************* |
| 3 | |
3 | |
| 4 | As of version 0.5, the psiconv package uses automake, autoconf and libtool. |
4 | Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free |
| 5 | This should make it possible to compile it on almost any architecture. |
5 | Software Foundation, Inc. |
| 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 | |
6 | |
| 11 | If your platform has no 32-bit integers (as int, long or long long), you |
7 | This file is free documentation; the Free Software Foundation gives |
| 12 | can forget about compiling libpsiconv. Sorry. |
8 | unlimited permission to copy, distribute and modify it. |
| 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 | |
9 | |
| 22 | Basic Installation |
10 | Basic Installation |
| 23 | ================== |
11 | ================== |
| 24 | |
12 | |
| 25 | These are generic installation instructions. |
13 | These are generic installation instructions. |
| 26 | |
14 | |
| 27 | The `configure' shell script attempts to guess correct values for |
15 | The `configure' shell script attempts to guess correct values for |
| 28 | various system-dependent variables used during compilation. It uses |
16 | various system-dependent variables used during compilation. It uses |
| 29 | those values to create a `Makefile' in each directory of the package. |
17 | 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 |
18 | It may also create one or more `.h' files containing system-dependent |
| 31 | definitions. Finally, it creates a shell script `config.status' that |
19 | definitions. Finally, it creates a shell script `config.status' that |
| 32 | you can run in the future to recreate the current configuration, a file |
20 | 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 |
21 | file `config.log' containing compiler output (useful mainly for |
| 34 | reconfiguring, and a file `config.log' containing compiler output |
22 | debugging `configure'). |
| 35 | (useful mainly for debugging `configure'). |
23 | |
|
|
24 | It can also use an optional file (typically called `config.cache' |
|
|
25 | and enabled with `--cache-file=config.cache' or simply `-C') that saves |
|
|
26 | the results of its tests to speed up reconfiguring. (Caching is |
|
|
27 | disabled by default to prevent problems with accidental use of stale |
|
|
28 | cache files.) |
| 36 | |
29 | |
| 37 | If you need to do unusual things to compile the package, please try |
30 | 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 |
31 | 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 |
32 | 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' |
33 | 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. |
34 | some point `config.cache' contains results you don't want to keep, you |
|
|
35 | may remove or edit it. |
| 42 | |
36 | |
| 43 | The file `configure.in' is used to create `configure' by a program |
37 | The file `configure.ac' (or `configure.in') is used to create |
| 44 | called `autoconf'. You only need `configure.in' if you want to change |
38 | `configure' by a program called `autoconf'. You only need |
| 45 | it or regenerate `configure' using a newer version of `autoconf'. |
39 | `configure.ac' if you want to change it or regenerate `configure' using |
|
|
40 | a newer version of `autoconf'. |
| 46 | |
41 | |
| 47 | The simplest way to compile this package is: |
42 | The simplest way to compile this package is: |
| 48 | |
43 | |
| 49 | 1. `cd' to the directory containing the package's source code and type |
44 | 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 |
45 | `./configure' to configure the package for your system. If you're |
| … | |
… | |
| 73 | with the distribution. |
68 | with the distribution. |
| 74 | |
69 | |
| 75 | Compilers and Options |
70 | Compilers and Options |
| 76 | ===================== |
71 | ===================== |
| 77 | |
72 | |
| 78 | Some systems require unusual options for compilation or linking that |
73 | Some systems require unusual options for compilation or linking that the |
| 79 | the `configure' script does not know about. You can give `configure' |
74 | `configure' script does not know about. Run `./configure --help' for |
| 80 | initial values for variables by setting them in the environment. Using |
75 | 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 | |
76 | |
| 85 | Or on systems that have the `env' program, you can do it like this: |
77 | You can give `configure' initial values for configuration parameters |
| 86 | env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure |
78 | by setting variables in the command line or in the environment. Here |
|
|
79 | is an example: |
|
|
80 | |
|
|
81 | ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix |
|
|
82 | |
|
|
83 | *Note Defining Variables::, for more details. |
| 87 | |
84 | |
| 88 | Compiling For Multiple Architectures |
85 | Compiling For Multiple Architectures |
| 89 | ==================================== |
86 | ==================================== |
| 90 | |
87 | |
| 91 | You can compile the package for more than one kind of computer at the |
88 | You can compile the package for more than one kind of computer at the |
| 92 | same time, by placing the object files for each architecture in their |
89 | same time, by placing the object files for each architecture in their |
| 93 | own directory. To do this, you must use a version of `make' that |
90 | own directory. To do this, you must use a version of `make' that |
| 94 | supports the `VPATH' variable, such as GNU `make'. `cd' to the |
91 | 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 |
92 | directory where you want the object files and executables to go and run |
| 96 | the `configure' script. `configure' automatically checks for the |
93 | the `configure' script. `configure' automatically checks for the |
| 97 | source code in the directory that `configure' is in and in `..'. |
94 | source code in the directory that `configure' is in and in `..'. |
| 98 | |
95 | |
| 99 | If you have to use a `make' that does not supports the `VPATH' |
96 | 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 |
97 | 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 |
98 | time in the source code directory. After you have installed the |
| 102 | one architecture, use `make distclean' before reconfiguring for another |
99 | package for one architecture, use `make distclean' before reconfiguring |
| 103 | architecture. |
100 | for another architecture. |
| 104 | |
101 | |
| 105 | Installation Names |
102 | Installation Names |
| 106 | ================== |
103 | ================== |
| 107 | |
104 | |
| 108 | By default, `make install' will install the package's files in |
105 | By default, `make install' will install the package's files in |
| 109 | `/usr/local/bin', `/usr/local/man', etc. You can specify an |
106 | `/usr/local/bin', `/usr/local/man', etc. You can specify an |
| 110 | installation prefix other than `/usr/local' by giving `configure' the |
107 | installation prefix other than `/usr/local' by giving `configure' the |
| 111 | option `--prefix=PATH'. |
108 | option `--prefix=PREFIX'. |
| 112 | |
109 | |
| 113 | You can specify separate installation prefixes for |
110 | You can specify separate installation prefixes for |
| 114 | architecture-specific files and architecture-independent files. If you |
111 | architecture-specific files and architecture-independent files. If you |
| 115 | give `configure' the option `--exec-prefix=PATH', the package will use |
112 | give `configure' the option `--exec-prefix=PREFIX', the package will |
| 116 | PATH as the prefix for installing programs and libraries. |
113 | use PREFIX as the prefix for installing programs and libraries. |
| 117 | Documentation and other data files will still use the regular prefix. |
114 | Documentation and other data files will still use the regular prefix. |
| 118 | |
115 | |
| 119 | In addition, if you use an unusual directory layout you can give |
116 | In addition, if you use an unusual directory layout you can give |
| 120 | options like `--bindir=PATH' to specify different values for particular |
117 | options like `--bindir=DIR' to specify different values for particular |
| 121 | kinds of files. Run `configure --help' for a list of the directories |
118 | kinds of files. Run `configure --help' for a list of the directories |
| 122 | you can set and what kinds of files go in them. |
119 | you can set and what kinds of files go in them. |
| 123 | |
120 | |
| 124 | If the package supports it, you can cause programs to be installed |
121 | If the package supports it, you can cause programs to be installed |
| 125 | with an extra prefix or suffix on their names by giving `configure' the |
122 | with an extra prefix or suffix on their names by giving `configure' the |
| 126 | option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. |
123 | option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. |
| 127 | |
124 | |
| 128 | Optional Features |
125 | Optional Features |
| 129 | ================= |
126 | ================= |
| 130 | |
127 | |
| 131 | Some packages pay attention to `--enable-FEATURE' options to |
128 | Some packages pay attention to `--enable-FEATURE' options to |
| 132 | `configure', where FEATURE indicates an optional part of the package. |
129 | `configure', where FEATURE indicates an optional part of the package. |
| 133 | They may also pay attention to `--with-PACKAGE' options, where PACKAGE |
130 | They may also pay attention to `--with-PACKAGE' options, where PACKAGE |
| 134 | is something like `gnu-as' or `x' (for the X Window System). The |
131 | is something like `gnu-as' or `x' (for the X Window System). The |
| 135 | `README' should mention any `--enable-' and `--with-' options that the |
132 | `README' should mention any `--enable-' and `--with-' options that the |
| 136 | package recognizes. |
133 | package recognizes. |
| … | |
… | |
| 141 | `--x-libraries=DIR' to specify their locations. |
138 | `--x-libraries=DIR' to specify their locations. |
| 142 | |
139 | |
| 143 | Specifying the System Type |
140 | Specifying the System Type |
| 144 | ========================== |
141 | ========================== |
| 145 | |
142 | |
| 146 | There may be some features `configure' can not figure out |
143 | There may be some features `configure' cannot figure out automatically, |
| 147 | automatically, but needs to determine by the type of host the package |
144 | but needs to determine by the type of machine the package will run on. |
|
|
145 | Usually, assuming the package is built to be run on the _same_ |
| 148 | will run on. Usually `configure' can figure that out, but if it prints |
146 | architectures, `configure' can figure that out, but if it prints a |
| 149 | a message saying it can not guess the host type, give it the |
147 | message saying it cannot guess the machine type, give it the |
| 150 | `--host=TYPE' option. TYPE can either be a short name for the system |
148 | `--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: |
149 | type, such as `sun4', or a canonical name which has the form: |
|
|
150 | |
| 152 | CPU-COMPANY-SYSTEM |
151 | CPU-COMPANY-SYSTEM |
| 153 | |
152 | |
|
|
153 | where SYSTEM can have one of these forms: |
|
|
154 | |
|
|
155 | OS KERNEL-OS |
|
|
156 | |
| 154 | See the file `config.sub' for the possible values of each field. If |
157 | 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 |
158 | `config.sub' isn't included in this package, then this package doesn't |
| 156 | need to know the host type. |
159 | need to know the machine type. |
| 157 | |
160 | |
| 158 | If you are building compiler tools for cross-compiling, you can also |
161 | 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 |
162 | 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 |
163 | produce code for. |
| 161 | system on which you are compiling the package. |
164 | |
|
|
165 | If you want to _use_ a cross compiler, that generates code for a |
|
|
166 | platform different from the build platform, you should specify the |
|
|
167 | "host" platform (i.e., that on which the generated programs will |
|
|
168 | eventually be run) with `--host=TYPE'. |
| 162 | |
169 | |
| 163 | Sharing Defaults |
170 | Sharing Defaults |
| 164 | ================ |
171 | ================ |
| 165 | |
172 | |
| 166 | If you want to set default values for `configure' scripts to share, |
173 | If you want to set default values for `configure' scripts to share, you |
| 167 | you can create a site shell script called `config.site' that gives |
174 | can create a site shell script called `config.site' that gives default |
| 168 | default values for variables like `CC', `cache_file', and `prefix'. |
175 | values for variables like `CC', `cache_file', and `prefix'. |
| 169 | `configure' looks for `PREFIX/share/config.site' if it exists, then |
176 | `configure' looks for `PREFIX/share/config.site' if it exists, then |
| 170 | `PREFIX/etc/config.site' if it exists. Or, you can set the |
177 | `PREFIX/etc/config.site' if it exists. Or, you can set the |
| 171 | `CONFIG_SITE' environment variable to the location of the site script. |
178 | `CONFIG_SITE' environment variable to the location of the site script. |
| 172 | A warning: not all `configure' scripts look for a site script. |
179 | A warning: not all `configure' scripts look for a site script. |
| 173 | |
180 | |
| 174 | Operation Controls |
181 | Defining Variables |
| 175 | ================== |
182 | ================== |
| 176 | |
183 | |
|
|
184 | Variables not defined in a site shell script can be set in the |
|
|
185 | environment passed to `configure'. However, some packages may run |
|
|
186 | configure again during the build, and the customized values of these |
|
|
187 | variables may be lost. In order to avoid this problem, you should set |
|
|
188 | them in the `configure' command line, using `VAR=value'. For example: |
|
|
189 | |
|
|
190 | ./configure CC=/usr/local2/bin/gcc |
|
|
191 | |
|
|
192 | will cause the specified gcc to be used as the C compiler (unless it is |
|
|
193 | overridden in the site shell script). |
|
|
194 | |
|
|
195 | `configure' Invocation |
|
|
196 | ====================== |
|
|
197 | |
| 177 | `configure' recognizes the following options to control how it |
198 | `configure' recognizes the following options to control how it operates. |
| 178 | operates. |
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. |
| 179 | |
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 | |
Parent Directory
| 
Revision Log
| 
Patch