mirrors/prosody
1
0
Fork 0
mirror of https://github.com/bjc/prosody.git synced 2025-04-03 05:07:42 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions

INSTALL: Update from site version

Browse source
This commit is contained in:
Kim Alvefur 2022-01-28 11:57:58 +01:00
parent dccab4e10f
commit f5d2ee89b1
1 changed files with 44 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

82
INSTALL
View file

@ -1,73 +1,79 @@
(This file was created from (This file was created from
https://prosody.im/doc/installing_from_source on 2013-03-31) https://prosody.im/doc/installing_from_source on 2013-03-31)
====== Installing from source ====== # Installing from source
==== Dependencies ====
There are a couple of libraries which Prosody needs installed before
you can build it. These are:
* lua5.1: The Lua 5.1 interpreter ## Dependencies
* liblua5.1: Lua 5.1 library
* libssl 0.9.8: OpenSSL
* libidn11: GNU libidn library, version 1.1
These can be installed on Debian/Ubuntu with the packages: lua5.1 There are a couple of development packages which Prosody needs installed
liblua5.1-dev libidn11-dev libssl-dev before you can build it. These are:
On Mandriva try: urpmi lua liblua-devel libidn-devel libopenssl-devel - The [Lua](http://lua.org/) library, version 5.4 recommended
- [OpenSSL](http://openssl.org/)
- String processing library, one of
- [ICU](https://icu.unicode.org/) (recommended)
- [GNU libidn](http://www.gnu.org/software/libidn/)
On other systems... good luck, but please let me know of the best way These can be installed on Debian/Ubuntu by running
of getting the dependencies for your system and I can add it here. `apt-get build-dep prosody` or by installing the packages
`liblua5.4-dev`, `libicu-dev` and `libssl-dev`.
==== configure ==== On Mandriva try:
The first step of building is to run the configure script. This
creates a file called 'config.unix' which is used by the next step to
control aspects of the build process.
All options to configure can be seen by running ./configure --help. urpmi lua liblua-devel libidn-devel libopenssl-devel
Sometimes you won't need to pass any parameters to configure, but on
most systems you shall.
To make this a little easier, there are a few presets which configure On Mac OS X, if you have MacPorts installed, you can try:
accepts. You can load a preset using:
./configure --ostype=PRESET sudo port install lua lua-luasocket lua-luasec lua-luaexpat
Where PRESET can currently be one of: 'debian', 'macosx' or (in 0.8 On other systems... good luck, but please let us know of the best way of
and later) 'freebsd' getting the dependencies for your system and we can add it here.
## configure
The first step of building is to run the configure script. This creates
a file called 'config.unix' which is used by the next step to control
aspects of the build process.
./configure
All options to configure can be seen by running
./configure --help
## make
==== make ====
Once you have run configure successfully, then you can simply run: Once you have run configure successfully, then you can simply run:
make make
Simple? :-) Simple? :-)
If you do happen to have problems at this stage, it is most likely If you do happen to have problems at this stage, it is most likely due
due to the build process not finding the dependencies. Ensure you to the build process not finding the dependencies. Ensure you have them
have them installed, and in the standard library paths for your installed, and in the standard library paths for your system.
system.
For more help, just ask ;-) For more help, just ask ;-)
==== install ==== ==== install ====
At this stage you should be able to run Prosody simply with: At this stage you should be able to run Prosody simply with:
./prosody ./prosody
There is no problem with this, it is actually the easiest way to do There is no problem with this, it is actually the easiest way to do
development, as it doesn't spread parts around your system, and you development, as it doesn't spread parts around your system, and you
can keep multiple versions around in their own directories without can keep multiple versions around in their own directories without
conflict. conflict.
Should you wish to install it system-wide however, simply run: Should you wish to install it system-wide however, simply run:
sudo make install sudo make install
...it will install into /usr/local/ by default. To change this you ...it will install into /usr/local/ by default. To change this you can
can pass to the initial ./configure using the 'prefix' option, or pass to the initial ./configure using the 'prefix' option, or edit
edit config.unix directly. If the new path doesn't require root config.unix directly. If the new path doesn't require root permission to
permission to write to, you also won't need (or want) to use 'sudo' write to, you also won't need (or want) to use 'sudo' in front of the
in front of the 'make install'. 'make install'.
Have fun, and see you on Jabber! Have fun, and see you on Jabber!