1
0
mirror of https://github.com/profanity-im/profanity.git synced 2024-12-04 14:46:46 -05:00
Go to file
j.r 5676159aa5
Fix python executed during configure
Previously it relied on AX_PYTHON_DEVEL, which in turn executes
python-config to get the build flags. However this does not work while
cross compiling because we can't execute the python-config build for the
target platform. To circumvent this problem the python build flags are
now queried via pkgconfig, which has the drawback of not having some
extra build flags, but they do not seem to be needed.

I tested this patch with the termux build system and it build without
their existing hack of injecting python after the configure step. I also
tested non cross compile build on Arch Linux and it also still works.

Fixes #851
2022-02-18 19:45:31 +01:00
.builds Upgrade to OpenBSD 7.0 in CI 2021-12-24 13:49:07 +01:00
.github Add Pull Request template 2022-02-18 18:11:51 +01:00
apidocs fixed typo from "the Yes" to "to YES" 2022-02-03 14:25:25 +05:30
docs Start new cycle 2021-09-28 19:53:05 +02:00
icons better, final icons 2016-03-09 12:55:57 +01:00
src Fix python executed during configure 2022-02-18 19:45:31 +01:00
tests auto-format 2022-02-01 15:01:28 +01:00
themes Add (experimental) theme snikket. 2021-10-16 14:08:21 +02:00
.clang-format auto-format 2022-02-01 15:01:28 +01:00
.codespellrc Add codespell config 2021-10-01 23:13:17 +02:00
.gitignore Add I/O error handling and use filenames instead of file descriptors 2020-11-16 21:58:09 +01:00
bootstrap.sh Add Travis CI tests for Arch, Debian and OSX/macOS 2019-06-06 13:58:26 +02:00
Brewfile Switch from Travis CI to GitHub Actions 2020-12-17 15:09:25 +01:00
CHANGELOG Release 0.11.1 2021-09-28 19:48:42 +02:00
ci-build.sh Upgrade to OpenBSD 7.0 in CI 2021-12-24 13:49:07 +01:00
configure-debug debug build: build without -fsanitize=address 2021-03-24 17:20:54 +01:00
configure.ac Fix python executed during configure 2022-02-18 19:45:31 +01:00
CONTRIBUTING.md Add unit tests section to CONTIBUTING.md 2022-02-18 18:49:43 +01:00
COPYING License: use upstream license file 2021-08-26 00:30:55 +00:00
Dockerfile.arch ci: remove building of stabber 2022-01-12 16:54:43 +01:00
Dockerfile.debian ci: dont verify ssl 2022-01-12 18:59:39 +01:00
Dockerfile.fedora ci: dont verify ssl 2022-01-12 18:59:39 +01:00
Dockerfile.tumbleweed ci: switch from libmesode to libstrophe 2021-10-28 20:13:41 +02:00
Dockerfile.ubuntu ci: dont verify ssl 2022-01-12 18:59:39 +01:00
LICENSE.txt Update copyright years 2019-04-24 01:08:38 +02:00
Makefile.am build: remove otr3 support 2022-02-18 14:01:28 +01:00
prof.supp Dirty fix libgcrypt memleak 2019-07-11 14:25:42 +02:00
profrc.example XEP-0392: config: add "color.nick" bool option 2019-12-03 21:10:39 +01:00
README.md Remove Patreon 2022-02-16 12:21:18 +01:00
RELEASE_GUIDE.md Fix spelling 2021-08-26 01:17:42 +00:00
SPONSORS.md sponsors: Add Matteo Bini 2021-05-12 16:50:45 +02:00
theme_template Make 'scrolled' themeable 2020-05-21 09:16:18 +02:00

Profanity

Build Status builds.sr.ht status Packaging status GitHub contributors

Profanity is a console based XMPP client inspired by Irssi.

If you like Profanity consider becoming a sponsor or donate some money.

alt tag

See the User Guide for information on installing and using Profanity.

Project

This project is about freedom, privacy and choice. We want to enable people to chat with one another in a safe way. Thus supporting encryption (OTR, PGP, OMEMO, OX) and being decentralized, meaning everyone can run their own server. We believe XMPP is a great proven protocol with an excellent community serving this purpose well.

Feel free to follow us on twitter, join our mailing list and/or MUC.

Installation

Our user guide contains an install section and a section for building from source yourself.

Donations

We would highly appreciate it if you support us via GitHub Sponsors. Especially if you make feature requests or need help using Profanity. Sponsoring enables us to spend time on Profanity.

An alternative way to support us would be to ask for our IBAN.

Issues backed by a sponsor will be tagged with the sponsored label. Feature requests that we consider out of scope, either because of interest or because of time needed to implement them, will be marked with the unfunded label.

Another way to sponsor us or get an issue solved is to create a bug bounty. Here one sets a bounty on a certain task and once the task is completed you send the money to the person who did the work.

Tasks from our sponsors will be tackled first.

Thank you! <3

How to contribute

We tried to sum things up on our helpout page. Additionally you can check out our blog where we have articles like: How to get a backtrace and Contributing a Patch via GitHub. For more technical details check out our CONTRIBUTING.md file.

Getting help

To get help, first read our User Guide then check out the FAQ. If you have are having a problem then first search the issue tracker. If you don't find anything there either come to our MUC or create a new issue depending on what your problem is.

Website

URL: https://profanity-im.github.io

Repo: https://github.com/profanity-im/profanity-im.github.io

Blog

URL: https://profanity-im.github.io/blog

Repo: https://github.com/profanity-im/blog

Mailinglist

Mailing List: https://lists.notraces.net/mailman/listinfo/profanity

Chatroom

MUC: profanity@rooms.dismail.de

Plugins

Plugins repository: https://github.com/profanity-im/profanity-plugins