Debian Codegraph @

INSTALL

raw
1 Basic Installation
2 ==================
3
4 These are generic installation instructions.
5
6 The `configure' shell script attempts to guess correct values for
7 various system-dependent variables used during compilation. It uses
8 those values to create a `Makefile' in each directory of the package.
9 It may also create one or more `.h' files containing system-dependent
10 definitions. Finally, it creates a shell script `config.status' that
11 you can run in the future to recreate the current configuration, a file
12 `config.cache' that saves the results of its tests to speed up
13 reconfiguring, and a file `config.log' containing compiler output
14 (useful mainly for debugging `configure').
15
16 If you need to do unusual things to compile the package, please try
17 to figure out how `configure' could check whether to do them, and mail
18 diffs or instructions to the address given in the `README' so they can
19 be considered for the next release. If at some point `config.cache'
20 contains results you don't want to keep, you may remove or edit it.
21
22 The file `configure.ac' is used to create `configure' by a program
23 called `autoconf'. You only need `configure.ac' if you want to change
24 it or regenerate `configure' using a newer version of `autoconf'.
25
26 The simplest way to compile this package is:
27
28 1. `cd' to the directory containing the package's source code and
29 type `sh ./bootstrap.sh', then type `./configure' to configure the
30 package for your system.
31
32 Running `configure' takes awhile. While running, it prints some
33 messages telling which features it is checking for.
34
35 2. Type `make' to compile the package.
36
37 3. Optionally, type `make check' to run any self-tests that come with
38 the package.
39
40 4. Type `make install' to install the programs and any data files and
41 documentation.
42
43 5. You can remove the program binaries and object files from the
44 source code directory by typing `make clean'. To also remove the
45 files that `configure' created (so you can compile the package for
46 a different kind of computer), type `make distclean'. There is
47 also a `make maintainer-clean' target, but that is intended mainly
48 for the package's developers. If you use it, you may have to get
49 all sorts of other programs in order to regenerate files that came
50 with the distribution.
51
52 Compilers and Options
53 =====================
54
55 Some systems require unusual options for compilation or linking that
56 the `configure' script does not know about. You can give `configure'
57 initial values for variables by setting them in the environment. Using
58 a Bourne-compatible shell, you can do that on the command line like
59 this:
60 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
61
62 Or on systems that have the `env' program, you can do it like this:
63 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
64
65 Compiling For Multiple Architectures
66 ====================================
67
68 You can compile the package for more than one kind of computer at the
69 same time, by placing the object files for each architecture in their
70 own directory. To do this, you must use a version of `make' that
71 supports the `VPATH' variable, such as GNU `make'. `cd' to the
72 directory where you want the object files and executables to go and run
73 the `configure' script. `configure' automatically checks for the
74 source code in the directory that `configure' is in and in `..'.
75
76 If you have to use a `make' that does not supports the `VPATH'
77 variable, you have to compile the package for one architecture at a time
78 in the source code directory. After you have installed the package for
79 one architecture, use `make distclean' before reconfiguring for another
80 architecture.
81
82 Installation Names
83 ==================
84
85 By default, `make install' will install the pkcs11 API in the directory
86 `/usr/lib/pkcs11/', any STDLLs that were built in `/usr/lib/pkcs11/stdll',
87 the config programs in `/usr/lib/pkcs11/methods', and the slot daemon in
88 `/usr/sbin/'. You can specify an installation prefix other than `/usr/local'
89 bygiving `configure' the option `--prefix=PATH'.
90
91 Optional Features
92 =================
93
94 For packages that use the X Window System, `configure' can usually
95 find the X include and library files automatically, but if it doesn't,
96 you can use the `configure' options `--x-includes=DIR' and
97 `--x-libraries=DIR' to specify their locations.
98
99 Note: Do not specify 'prefix=/foo/bar', 'libdir=/foo/bar' with
100 the 'make' invocation. Specify them with 'configure' instead. Specifying
101 them with 'make' is not supported by the openCryptoki package and may
102 produce unexpected results!
103
104 Specifying the System Type
105 ==========================
106
107 There may be some features `configure' can not figure out
108 automatically, but needs to determine by the type of host the package
109 will run on. Usually `configure' can figure that out, but if it prints
110 a message saying it can not guess the host type, give it the
111 `--host=TYPE' option. TYPE can either be a short name for the system
112 type, such as `sun4', or a canonical name with three fields:
113 CPU-COMPANY-SYSTEM
114
115 See the file `config.sub' for the possible values of each field. If
116 `config.sub' isn't included in this package, then this package doesn't
117 need to know the host type.
118
119 If you are building compiler tools for cross-compiling, you can also
120 use the `--target=TYPE' option to select the type of system they will
121 produce code for and the `--build=TYPE' option to select the type of
122 system on which you are compiling the package.
123
124 Sharing Defaults
125 ================
126
127 If you want to set default values for `configure' scripts to share,
128 you can create a site shell script called `config.site' that gives
129 default values for variables like `CC', `cache_file', and `prefix'.
130 `configure' looks for `PREFIX/share/config.site' if it exists, then
131 `PREFIX/etc/config.site' if it exists. Or, you can set the
132 `CONFIG_SITE' environment variable to the location of the site script.
133 A warning: not all `configure' scripts look for a site script.
134
135 Operation Controls
136 ==================
137
138 `configure' recognizes the following options to control how it
139 operates.
140
141 `--cache-file=FILE'
142 Use and save the results of the tests in FILE instead of
143 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
144 debugging `configure'.
145
146 `--help'
147 Print a summary of the options to `configure', and exit.
148
149 `--quiet'
150 `--silent'
151 `-q'
152 Do not print messages saying which checks are being made. To
153 suppress all normal output, redirect it to `/dev/null' (any error
154 messages will still be shown).
155
156 `--srcdir=DIR'
157 Look for the package's source code in directory DIR. Usually
158 `configure' can determine that directory automatically.
159
160 `--version'
161 Print the version of Autoconf used to generate the `configure'
162 script, and exit.
163
164 `configure' also accepts some other, not widely useful, options.