about summary refs log tree commit diff stats
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* Improve macOS Readline checksCarlo Cabrera2021-11-241-4/+4
| | | | | | | | | Instead of checking for `lib` directories, let's make sure `libreadline` exists. Also, let's improve the error message if we can't find it. Finally, since we're only looking for `brew` on macOS, we don't need to use `$PATH_SEPARATOR` since we know what the path separator is.
* Make readline check more portableCarlo Cabrera2021-11-231-3/+12
| | | | | | | | | | | Currently, `configure.ac` assumes Readline is installed via Homebrew in `/usr/local`. This doesn't work for Homebrew on Apple Silicon, or MacPorts. Let's fix this by checking for a `brew` installation, and querying that for Readline's prefix if available. If not, it checks for an existing MacPorts prefix, and finally falls back to checking `/usr/local` in case a user installed Readline for themselves there.
* bump libstrophe requirement to 0.11.0Michael Vetter2021-10-281-1/+1
|
* ran `autoupdate`Steffen Jaeckel2021-10-271-2/+2
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* first step to remove libmesodeSteffen Jaeckel2021-10-271-11/+4
| | | | Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
* Remove Ruby commentMichael Vetter2021-09-291-2/+0
| | | | | | There most likely won't ever be Ruby plugins. Regards https://github.com/profanity-im/profanity/issues/779
* Look for plugins to install in global locationMichael Vetter2021-09-291-10/+18
| | | | | | | | | | | | | | | | | | Two options to install plugins. Mention the whole path: `/plugins install ~/src/profanity-plugins/my.py` Mention only the plugin name: `/plugins install my.py` The latter will look in `/usr/local/share/profanity/plugins/` for the file and copy it over to `~/.local/share/profanity/plugins`. At first I was thinking about loading the plugins from the global location. But users most likely don't want to have all plugins activated that an admin installs on a system. Regards https://github.com/profanity-im/profanity/issues/945
* Start new cycleMichael Vetter2021-09-281-2/+2
|
* Release 0.11.1Michael Vetter2021-09-281-2/+2
|
* Check for curl version nrMichael Vetter2021-07-201-1/+1
| | | | | | | We use `curl_url()` since e9d587578 which according to https://curl.se/libcurl/c/curl_url.html is only available in libcurl >= 7.62.0 . Related to https://github.com/profanity-im/profanity/issues/1581
* Start next cycleMichael Vetter2021-07-141-1/+1
|
* Release 0.11.0Michael Vetter2021-07-141-2/+2
|
* Start new cycleMichael Vetter2021-01-091-1/+1
|
* Release 0.10.0Michael Vetter2021-01-091-2/+2
|
* configure: check for python3-configMichael Vetter2020-10-091-1/+2
|
* Use g_date_time_format_iso8601()Michael Vetter2020-09-301-2/+2
| | | | | | | | | This partly reverts d3a387a0ec6e5265f625de87318be2de610efb01. For proanity 0.9.x we still wanted to support older glib versions so that we can be packaged for various linux distros. Now with 0.10 we want to move on.
* Require libstrophe/libmesode 0.10.0Michael Vetter2020-09-301-10/+2
|
* Basic support for building on NetBSD.nia2020-09-041-9/+13
| | | | | | - Add NetBSD as a recognized platform without -ldl. - Allow building with NetBSD libcurses instead of ncurses. - Portability to NetBSD sh - use POSIX '=' instead of '=='.
* configure: support gtk3 tooMichael Vetter2020-08-041-3/+5
| | | | | Make Profanity compilable with gtk2 and gtk3. Prefer the latter.
* 0.9.5Michael Vetter2020-07-011-1/+1
|
* Start new cycleMichael Vetter2020-06-241-1/+1
|
* Release 0.9.4Michael Vetter2020-06-241-2/+2
|
* Start new cycleMichael Vetter2020-06-191-1/+1
|
* Release 0.9.3Michael Vetter2020-06-191-2/+2
|
* Start new cycleMichael Vetter2020-06-131-1/+1
|
* Release 0.9.2Michael Vetter2020-06-131-2/+2
|
* Use gnu99 standardMichael Vetter2020-06-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With recent changes to c99 and -D_POSIX_C_SOURCE=200809L we get the following: openSUSE TW CI sais: ``` Now you can run `make' to build profanity In file included from /usr/include/python2.7/Python.h:8, from src/plugins/python_plugins.c:37: /usr/include/python2.7/pyconfig.h:1226: error: "_POSIX_C_SOURCE" redefined [-Werror] 1226 | #define _POSIX_C_SOURCE 200112L | <command-line>: note: this is the location of the previous definition In file included from /usr/include/python2.7/Python.h:8, from src/plugins/python_api.c:37: /usr/include/python2.7/pyconfig.h:1226: error: "_POSIX_C_SOURCE" redefined [-Werror] 1226 | #define _POSIX_C_SOURCE 200112L | <command-line>: note: this is the location of the previous definition cc1: all warnings being treated as errors ``` OpenBSD CI sais: ``` cc1: warnings being treated as errors src/database.c: In function 'log_database_get_previous_chat': src/database.c:226: warning: implicit declaration of function 'asprintf' gmake[1]: *** [Makefile:1924: src/database.o] Error 1 gmake[1]: Leaving directory '/home/build/profanity' gmake: *** [Makefile:1211: all] Error 2 ``` Let us use gnu99. Has been proposed before already and is fine. Regards https://github.com/profanity-im/profanity/issues/1357 Regards https://github.com/profanity-im/profanity/pull/1351
* Define POSIX macro to have strdupMichael Vetter2020-06-121-1/+1
| | | | | | | | | | | | | | https://github.com/profanity-im/profanity/commit/98c38dc6d6d29333c63f80327774f094610d8602 sets C99 as standard. strdup() is not part of C99. For now set `-D_POSIX_C_SOURCE=200809L` macro to have strdup() in C99. Using `gnu99` instead would be another option. We should take more care to use glib functions whenever possible. Regards https://github.com/profanity-im/profanity/issues/1357
* Start new cycleMichael Vetter2020-06-111-1/+1
|
* Release 0.9.1Michael Vetter2020-06-111-2/+2
|
* Make legacy auth optionalDmitry Podgorny2020-06-111-1/+10
| | | | | | | | Some systems don't provide recent libstrophe releases. When older version of libstrophe is detected, don't build legacy auth support. To simplify this patch, report about unsupported legacy auth and keep commands option as is.
* Start new cycleMichael Vetter2020-06-091-1/+1
|
* Release 0.9.0Michael Vetter2020-06-091-2/+2
|
* Bump libstrophe requirement to 0.9.3Michael Vetter2020-06-051-3/+3
| | | | | legacy auth (ac410445af65b9d332d4606a08ff549672042766) requires libstrophe 0.9.3 because of XMPP_CONN_FLAG_LEGACY_AUTH.
* Correctly check for 'expect'Michael Vetter2020-06-041-1/+1
| | | | | The expect library doesnt export 'main'. But it exports (and we use) exp_expectl.
* Merge pull request #1351 from toogley/masterMichael Vetter2020-06-041-1/+1
|\ | | | | Use always c99
| * use always c99; fixes "universal character names" error msgtoogley2020-06-021-1/+1
| | | | | | | | | | | | | | | | | | without this, i receive this error on openbsd 6.7: src/event/server_events.c:1477:19: error: universal character names are only valid in C++ and C99 src/event/server_events.c:1478:19: error: universal character names are only valid in C++ and C99 gmake[1]: *** [Makefile:1925: src/event/server_events.o] Error 1 gmake[1]: Leaving directory '/home/toogley/profanity' gmake: *** [Makefile:1212: all] Error 2
* | Merge pull request #1349 from profanity-im/autotoolsMichael Vetter2020-06-031-2/+18
|\ \ | |/ |/| configure.ac: add additional check for libstrophe
| * Include mesode.h in libmesode test caseMichael Vetter2020-06-031-0/+5
| | | | | | | | Regards https://github.com/profanity-im/profanity/issues/1334
| * configure.ac: add additional check for libstropheDmitry Podgorny2020-05-311-2/+13
| | | | | | | | | | | | | | | | | | After the library is found by pkg-config, try to build a simple program to check the installation. The motivation of this check is that the chance that users manually install libstrophe/libmesode is higher than for other libs. Fixes #1334.
* | Fix: configure sqliteDebXWoody2020-05-301-1/+1
|/
* Downgrade sqlite to 3.22.0Michael Vetter2020-04-081-2/+2
| | | | | | | Last version in Ubuntu LTS (bionic 18.04). I think we don't use later functionality. Let's see. glib version fits.
* Downgrade dependenciesMichael Vetter2020-04-071-4/+4
| | | | | | | | | | | Use g_date_time_format() instead of g_date_time_format_iso8601() to only rely on glib 2.56.0 which is the latest version in Debian Buster (current stable). We also only use basic sqlite functions so 3.27.0 should be fine there (also the one in Debian buster). Thanks to @DebXWoody.
* Require at least glib 2.62.Michael Vetter2020-04-061-2/+2
| | | | g_date_time_format_iso8601() is only in glib since 2.62.
* Require only sqlite 3.28.0Michael Vetter2020-04-061-2/+2
| | | | | We don't need newer features and so it runs on Leap 15.1 too. Let's see what Debian etc. need.
* Start SQLite db moduleMichael Vetter2020-04-061-2/+5
| | | | | | | | | | | | | | I plan to save all messages in an SQLite db. For retrieving information it's nicer than having it in a text file. We will have more info in there and easier to parse it. This will also be good for later MAM (https://github.com/profanity-im/profanity/issues/660). Regular text files will still be an option for users so that they can easily grep them and do whatever they like. Internally Profanity will only use the SQLite db.
* Add builds.sr.ht CI for OpenBSDWilliam Wennerström2020-02-171-7/+11
| | | | | | | | * Add .builds/openbsd.yml for builds.sr.ht * Update travis-build.sh -> ci-build.sh with OpenBSD case * Fix libdl check in configure.ac (OpenBSD has libdl built-in) * Fix some minor issues found when compiling on OpenBSD with GCC (e.g. uninitialized variables)
* Start next development cycleMichael Vetter2020-02-071-1/+1
|
* Release 0.8.1Michael Vetter2020-02-071-2/+2
|
* Start next development cycleMichael Vetter2020-02-031-1/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-12 03:09:34 +0000