Software /
code /
prosody
Comparison
INSTALL @ 12222:61592927335b
INSTALL: Update from site version
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 28 Jan 2022 11:57:58 +0100 |
parent | 7359:a5a080c12c96 |
child | 12286:ad88732eea51 |
comparison
equal
deleted
inserted
replaced
12221:056b7920b686 | 12222:61592927335b |
---|---|
1 (This file was created from | 1 (This file was created from |
2 https://prosody.im/doc/installing_from_source on 2013-03-31) | 2 https://prosody.im/doc/installing_from_source on 2013-03-31) |
3 | 3 |
4 ====== Installing from source ====== | 4 # Installing from source |
5 ==== Dependencies ==== | |
6 There are a couple of libraries which Prosody needs installed before | |
7 you can build it. These are: | |
8 | 5 |
9 * lua5.1: The Lua 5.1 interpreter | 6 ## Dependencies |
10 * liblua5.1: Lua 5.1 library | |
11 * libssl 0.9.8: OpenSSL | |
12 * libidn11: GNU libidn library, version 1.1 | |
13 | 7 |
14 These can be installed on Debian/Ubuntu with the packages: lua5.1 | 8 There are a couple of development packages which Prosody needs installed |
15 liblua5.1-dev libidn11-dev libssl-dev | 9 before you can build it. These are: |
16 | 10 |
17 On Mandriva try: urpmi lua liblua-devel libidn-devel libopenssl-devel | 11 - The [Lua](http://lua.org/) library, version 5.4 recommended |
12 - [OpenSSL](http://openssl.org/) | |
13 - String processing library, one of | |
14 - [ICU](https://icu.unicode.org/) (recommended) | |
15 - [GNU libidn](http://www.gnu.org/software/libidn/) | |
18 | 16 |
19 On other systems... good luck, but please let me know of the best way | 17 These can be installed on Debian/Ubuntu by running |
20 of getting the dependencies for your system and I can add it here. | 18 `apt-get build-dep prosody` or by installing the packages |
19 `liblua5.4-dev`, `libicu-dev` and `libssl-dev`. | |
21 | 20 |
22 ==== configure ==== | 21 On Mandriva try: |
23 The first step of building is to run the configure script. This | |
24 creates a file called 'config.unix' which is used by the next step to | |
25 control aspects of the build process. | |
26 | 22 |
27 All options to configure can be seen by running ./configure --help. | 23 urpmi lua liblua-devel libidn-devel libopenssl-devel |
28 Sometimes you won't need to pass any parameters to configure, but on | |
29 most systems you shall. | |
30 | 24 |
31 To make this a little easier, there are a few presets which configure | 25 On Mac OS X, if you have MacPorts installed, you can try: |
32 accepts. You can load a preset using: | |
33 | 26 |
34 ./configure --ostype=PRESET | 27 sudo port install lua lua-luasocket lua-luasec lua-luaexpat |
35 | 28 |
36 Where PRESET can currently be one of: 'debian', 'macosx' or (in 0.8 | 29 On other systems... good luck, but please let us know of the best way of |
37 and later) 'freebsd' | 30 getting the dependencies for your system and we can add it here. |
38 | 31 |
39 ==== make ==== | 32 ## configure |
33 | |
34 The first step of building is to run the configure script. This creates | |
35 a file called 'config.unix' which is used by the next step to control | |
36 aspects of the build process. | |
37 | |
38 ./configure | |
39 | |
40 All options to configure can be seen by running | |
41 | |
42 ./configure --help | |
43 | |
44 ## make | |
45 | |
40 Once you have run configure successfully, then you can simply run: | 46 Once you have run configure successfully, then you can simply run: |
41 | 47 |
42 make | 48 make |
43 | 49 |
44 Simple? :-) | 50 Simple? :-) |
45 | 51 |
46 If you do happen to have problems at this stage, it is most likely | 52 If you do happen to have problems at this stage, it is most likely due |
47 due to the build process not finding the dependencies. Ensure you | 53 to the build process not finding the dependencies. Ensure you have them |
48 have them installed, and in the standard library paths for your | 54 installed, and in the standard library paths for your system. |
49 system. | |
50 | 55 |
51 For more help, just ask ;-) | 56 For more help, just ask ;-) |
52 | 57 |
53 ==== install ==== | 58 ==== install ==== |
59 | |
54 At this stage you should be able to run Prosody simply with: | 60 At this stage you should be able to run Prosody simply with: |
55 | 61 |
56 ./prosody | 62 ./prosody |
57 | 63 |
58 There is no problem with this, it is actually the easiest way to do | 64 There is no problem with this, it is actually the easiest way to do |
59 development, as it doesn't spread parts around your system, and you | 65 development, as it doesn't spread parts around your system, and you |
60 can keep multiple versions around in their own directories without | 66 can keep multiple versions around in their own directories without |
61 conflict. | 67 conflict. |
62 | 68 |
63 Should you wish to install it system-wide however, simply run: | 69 Should you wish to install it system-wide however, simply run: |
64 | 70 |
65 sudo make install | 71 sudo make install |
66 | 72 |
67 ...it will install into /usr/local/ by default. To change this you | 73 ...it will install into /usr/local/ by default. To change this you can |
68 can pass to the initial ./configure using the 'prefix' option, or | 74 pass to the initial ./configure using the 'prefix' option, or edit |
69 edit config.unix directly. If the new path doesn't require root | 75 config.unix directly. If the new path doesn't require root permission to |
70 permission to write to, you also won't need (or want) to use 'sudo' | 76 write to, you also won't need (or want) to use 'sudo' in front of the |
71 in front of the 'make install'. | 77 'make install'. |
72 | 78 |
73 Have fun, and see you on Jabber! | 79 Have fun, and see you on Jabber! |