1 (This file was created from
2 https://prosody.im/doc/installing_from_source on 2013-03-31)
4 ====== Installing from source ======
6 There are a couple of libraries which Prosody needs installed before
7 you can build it. These are:
9 * lua5.1: The Lua 5.1 interpreter
10 * liblua5.1: Lua 5.1 library
11 * libssl 0.9.8: OpenSSL
12 * libidn11: GNU libidn library, version 1.1
14 These can be installed on Debian/Ubuntu with the packages: lua5.1
15 liblua5.1-dev libidn11-dev libssl-dev
17 On Mandriva try: urpmi lua liblua-devel libidn-devel libopenssl-devel
19 On other systems... good luck, but please let me know of the best way
20 of getting the dependencies for your system and I can add it here.
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.
27 All options to configure can be seen by running ./configure --help.
28 Sometimes you won't need to pass any parameters to configure, but on
29 most systems you shall.
31 To make this a little easier, there are a few presets which configure
32 accepts. You can load a preset using:
34 ./configure --ostype=PRESET
36 Where PRESET can currently be one of: 'debian', 'macosx' or (in 0.8
40 Once you have run configure successfully, then you can simply run:
46 If you do happen to have problems at this stage, it is most likely
47 due to the build process not finding the dependencies. Ensure you
48 have them installed, and in the standard library paths for your
51 For more help, just ask ;-)
54 At this stage you should be able to run Prosody simply with:
58 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
60 can keep multiple versions around in their own directories without
63 Should you wish to install it system-wide however, simply run:
67 ...it will install into /usr/local/ by default. To change this you
68 can pass to the initial ./configure using the 'prefix' option, or
69 edit config.unix directly. If the new path doesn't require root
70 permission to write to, you also won't need (or want) to use 'sudo'
71 in front of the 'make install'.
73 Have fun, and see you on Jabber!