Changes in README.md [e26aa72:b5cc87e]
Legend:
- Unmodified
- Added
- Removed
-
README.md
re26aa72 rb5cc87e 16 16 License: GPLv2 17 17 18 ## Development18 ## Installation 19 19 20 Use github pull requests against the 'develop' branch to submit patches.20 BitlBee is available in the package managers of most distros. 21 21 22 The 'master' branch should be stable enough to be usable by users of the APT repo, but only requires a few days of testing in the 'develop' branch. 22 For debian/ubuntu/etc you may use the nightly APT repository: http://code.bitlbee.org/debian/ 23 23 24 Building: 24 You can also use a public server (such as `im.bitlbee.org`) instead of installing it: http://bitlbee.org/main.php/servers.html 25 25 26 ``` 27 ./configure --debug=1 28 # or, for a local install: 29 # ./configure --debug=1 --prefix=$HOME/bitlbee --config=$HOME/bitlbee --pidfile=$HOME/bitlbee/bitlbee.pid 26 ## Compiling 30 27 31 # Also try --asan=1 for AddressSanitizer 28 If you wish to compile it yourself, ensure you have the following packages and their headers: 32 29 33 make 30 * glib 2.16 or newer (not to be confused with glibc) 31 * gnutls 32 * python 2 or 3 (for the user guide) 34 33 35 BITLBEE_DEBUG=1 ./bitlbee -Dnv 36 ``` 34 Some optional features have additional dependencies, such as libpurple, libotr, libevent, etc. 35 NSS and OpenSSL are also available but not as well supported as GnuTLS. 37 36 38 See ./doc/README and ./doc/HACKING for more details. 37 Once you have the dependencies, building should be a matter of: 39 38 40 Mappings of bzr revisions to git commits (for historical purposes) are available in ./doc/git-bzr-rev-map 39 ./configure 40 make 41 sudo make install 42 43 ## Development tips 44 45 * To enable debug symbols: `./configure --debug=1` 46 * To get some additional debug output for some protocols: `BITLBEE_DEBUG=1 ./bitlbee -Dnv` 47 * Use github pull requests against the 'develop' branch to submit patches. 48 * The coding style based on K&R with tabs and 120 columns. See `./doc/uncrustify.cfg` for the parameters used to reformat the code. 49 * Mappings of bzr revisions to git commits (for historical purposes) are available in `./doc/git-bzr-rev-map` 50 * See also `./doc/README` and `./doc/HACKING` 41 51 42 52 ## Help? 43 53 44 Join **#BitlBee** on OFTC (**irc.oftc.net**) (OFTC, *not* FreeNode!) and flame us right in the face. :-)54 Join **#BitlBee** on OFTC (**irc.oftc.net**) (OFTC, *not* FreeNode!)
Note: See TracChangeset
for help on using the changeset viewer.