|
1
by Jean-Paul Calderone
initial source import |
1 |
INSTALLATION INSTRUCTIONS FOR pyOpenSSL |
2 |
------------------------------------------------------------------------------
|
|
3 |
||
4 |
I have tested this on Debian Linux systems (woody and sid), Solaris 2.6 and |
|
5 |
2.7. Others have successfully compiled it on Windows and NT. |
|
6 |
||
7 |
||
8 |
-- Building the Module on a Unix System --
|
|
9 |
||
10 |
pyOpenSSL uses distutils, so there really shouldn't be any problems. To build |
|
11 |
the library:
|
|
12 |
||
13 |
python setup.py build
|
|
14 |
||
15 |
If your OpenSSL header files aren't in /usr/include, you may need to supply |
|
16 |
the -I flag to let the setup script know where to look. The same goes for the |
|
17 |
libraries of course, use the -L flag. Note that build won't accept these |
|
18 |
flags, so you have to run first build_ext and then build! Example:
|
|
19 |
||
20 |
python setup.py build_ext -I/usr/local/ssl/include -L/usr/local/ssl/lib
|
|
21 |
python setup.py build
|
|
22 |
||
23 |
Now you should have a directory called OpenSSL that contains e.g. SSL.so and
|
|
24 |
__init__.py somewhere in the build dicrectory, so just:
|
|
25 |
||
26 |
python setup.py install
|
|
27 |
||
28 |
If you, for some arcane reason, don't want the module to appear in the |
|
29 |
site-packages directory, use the --prefix option. |
|
30 |
||
31 |
You can, of course, do |
|
32 |
||
33 |
python setup.py --help |
|
34 |
||
35 |
to find out more about how to use the script. |
|
36 |
||
37 |
||
38 |
-- Building the Module on a Windows System --
|
|
39 |
||
40 |
Big thanks to Itamar Shtull-Trauring and Oleg Orlov for their help with |
|
41 |
Windows build instructions. Same as for Unix systems, we have to separate |
|
42 |
the build_ext and the build. |
|
43 |
||
44 |
Building the library: |
|
45 |
||
46 |
setup.py build_ext -I ...\openssl\inc32 -L ...\openssl\out32dll |
|
47 |
setup.py build |
|
48 |
||
49 |
Where ...\openssl is of course the location of your OpenSSL installation. |
|
50 |
||
51 |
Installation is the same as for Unix systems: |
|
52 |
||
53 |
setup.py install |
|
54 |
||
55 |
And similarily, you can do |
|
56 |
||
57 |
setup.py --help |
|
58 |
||
59 |
to get more information. |
|
60 |
||
61 |
||
62 |
-- Documentation --
|
|
63 |
||
64 |
The documentation is written in LaTeX, using the standard Python templates, |
|
65 |
and tools to compile it into a number of forms are included. You need to |
|
66 |
supply things like dvips, latex2html yourself of course! |
|
67 |
||
68 |
To build the text, html, postscript or dvi forms of the documentation, this is |
|
69 |
what you do: |
|
70 |
||
71 |
cd doc |
|
72 |
# To make the text-only documentation: |
|
73 |
make text |
|
74 |
# To make the dvi form: |
|
75 |
make dvi |
|
76 |
||
77 |
It's as simple as that. Note that since Python's mkhowto script is used, if |
|
78 |
you do first ``make dvi'' and then ``make ps'', the dvi file will disappear. |
|
79 |
I included a special build target ``make all'' that will build all the |
|
80 |
documentation in an order that won't let anything disappear. |
|
81 |
||
82 |
||
83 |
@(#) $Id: INSTALL,v 1.7 2002/06/14 12:14:19 martin Exp $ |
|
84 |