diff options
| author | dequis <dx@dxzone.com.ar> | 2017-10-16 22:10:30 -0300 |
|---|---|---|
| committer | dequis <dx@dxzone.com.ar> | 2017-10-16 22:10:30 -0300 |
| commit | 1e264442a48f33a5933c49a2c0332e426dcdb4a1 (patch) | |
| tree | d55b3cd05c7739663d9467b84b249a41ee1a830e | |
| parent | 7dbd24d7e29c421701b43d8e8a4ffc5c9e1ecbf5 (diff) | |
| download | bitlbee-facebook-1e264442a48f33a5933c49a2c0332e426dcdb4a1.tar.gz bitlbee-facebook-1e264442a48f33a5933c49a2c0332e426dcdb4a1.tar.bz2 bitlbee-facebook-1e264442a48f33a5933c49a2c0332e426dcdb4a1.tar.xz | |
README: mention deps
| -rw-r--r-- | README | 13 |
1 files changed, 8 insertions, 5 deletions
@@ -17,18 +17,21 @@ https://jgeboski.github.io/ ## Building from source +The folowing packages are required: autoconf, automake, libtool, glib2, +json-glib, bitlbee (names may vary across distros) + +Example for debian-based systems: + + apt install build-essential autoconf automake libtool libglib2.0-dev libjson-glib-dev bitlbee-dev + Make sure bitlbee and its headers have been installed. If bitlbee came from the distribution's repository, it will most likely need the -development package, usually bitlbee-dev. +development package, like bitlbee-dev in the example above. If bitlbee was built by hand (or alike via a script), ensure the make target `install-dev` is invoked. This target is not called by default, and will install the headers that are needed. -Do *not* use the source tree headers unless you know what you are -doing. This can lead to mismatched header versions, which often times -will lead to bad things. - $ git clone https://github.com/bitlbee/bitlbee-facebook.git $ cd bitlbee-facebook |