about summary refs log tree commit diff stats
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
* Fix xscreensaver detectionPaul Fertser2023-01-111-2/+3
| | | | | | | | | In 28a9605a1 we migrated from AC_CHECK_LIB which defines HAVE_LIBXSS automatically. With pkg-config way you need it explicit. And also x11 is needed or else linking will fail missing XFree(). Patch provided by Paul Fertser and comitted by jubalh. Thanks Paul! Fix https://github.com/profanity-im/profanity/issues/1695
* Start new cycleMichael Vetter2022-10-121-1/+1
|
* Release 0.13.1Michael Vetter2022-10-121-2/+2
|
* Merge pull request #1753 from wahjava/masterMichael Vetter2022-09-191-2/+2
|\ | | | | Fix typo in configure.ac
| * Fix typo in configure.acAshish SHUKLA2022-09-151-2/+2
| | | | | | | | Signed-off-by: Ashish SHUKLA <ashish.is@lostca.se>
* | typo in configure: enable_gdk_pixbuf not enable_pixbufOmar Polo2022-09-151-2/+2
|/ | | | | Otherwise gdk-pixbuf is always added as dependency even if disabled, when found.
* Start new cycleMichael Vetter2022-09-131-1/+1
|
* Release 0.13.0Michael Vetter2022-09-131-2/+2
|
* Require libstrophe 0.12.2Michael Vetter2022-08-081-1/+1
| | | | | 0.12.2 has some important fixes. Let's require it so users don't stumble upon bugs like https://github.com/profanity-im/profanity/issues/1743
* build: otr cflags -> CFLAGSMichael Vetter2022-06-291-1/+1
|
* build: dont define HAVE_QRENCODE at all in case not presentMichael Vetter2022-05-311-2/+1
| | | | | | | | | | | | | | | | | | | | | | Before we got an error when libqrencode was not installed: `src/ui/console.c:52:10: fatal error: qrencode.h: No such file or directory` Which looked like HAVE_QRENCODE was true. config.status showed: `config.status:D["HAVE_QRENCODE"]=" 0"` Holger pointed to me that there is not just true and false but defined and undefined. So one solution was to use `#if HAVE_QRENCODE == 1` to check for the actual value. Or dont define HAVE_QRENCODE in the non present case at all. In all the other HAVE_ variables we use this approach. I think i at first chose the wrong way out of confusion with BUILD_ and HAVE_.
* build: set HAVE_QRENCODE only onceMichael Vetter2022-05-301-3/+1
| | | | and use CLFAGS not cflags
* Make qrencode optional and add to CIMichael Vetter2022-05-301-5/+10
|
* Add basic qrcode functionsMichael Vetter2022-05-301-0/+8
|
* Add pixbuf building to CIMichael Vetter2022-05-301-1/+2
|
* Final touches for `/avatar set`Michael Vetter2022-05-271-4/+3
|
* Add checks for whether gdk-pixbuf exists before using avatar setMarcoPolo-PasTonMolo2022-05-261-0/+11
|
* Fix xscreensaver detectionPaul Fertser2022-04-211-1/+2
| | | | | | | Using pkg-config to find libraries requires explicit mention of the relevant _CFLAGS and _LIBS variables. Fixes #1695.
* Start new cycleMichael Vetter2022-04-041-1/+1
|
* Release 0.12.1Michael Vetter2022-04-041-2/+2
|
* Start new cycleMichael Vetter2022-03-301-1/+1
|
* Release 0.12.0Michael Vetter2022-03-301-1/+1
|
* Add debug information to binaryPaul Fertser2022-03-281-0/+1
| | | | | | | | | | | | Option -ggdb3 (same as -g3) doesn't affect code-generation, just adds to the binary size of an executable. Automake strips installed binaries automatically when "make install-strip" is run so enabling this option permanently doesn't affect the end result while allowing for hassle-free interactive debugging. If one is running a stripped binary it's still possible to attach GDB by process PID and then use "file /path/to/unstripped/profanity" to get all symbols and lines data.
* Fix AM_CFLAGS assignments (including libstrophe flags)Paul Fertser2022-03-271-2/+2
| | | | | | | | Autoconf can pre-populate this variable with essential parameters so it should be appended to rather than overridden. While at it, don't miss to append CFLAGS for libstrope which is needed if it's installed to a non-default location.
* Fix autoconf warning about AC_CANONICAL_TARGET orderingPaul Fertser2022-03-271-1/+2
| | | | | | | | AM_INIT_AUTOMAKE requires AC_ARG_PROGRAM so should go after AC_CANONICAL_TARGET for proper program name mangling. This fixes "AC_ARG_PROGRAM was called before AC_CANONICAL_TARGET" warning as emitted by autoconf 2.69.
* build: Use CPPFLAGS for obsdMichael Vetter2022-02-231-1/+1
| | | | | | | | | | | | | | | Fixing build failure detected by sr.ht for OpenBSD: ``` src/ui/inputwin.c: In function '_inp_rl_startup_hook': src/ui/inputwin.c:444:5: error: implicit declaration of function 'rl_bind_keyseq'; did you mean 'rl_bind_key'? [-Werror=implicit-function-declaration] 444 | rl_bind_keyseq("\\e1", _inp_rl_win_1_handler); | ^~~~~~~~~~~~~~ | rl_bind_key cc1: all warnings being treated as errors ``` Seems like both OSX and OpenBSD need CPPFLAGS here.
* Remove link to python bugMichael Vetter2022-02-181-1/+1
| | | | | | Since 5676159aa52a734a34bf231b400ae13860e1012d the python_CPPFLAGS isn't needed anymore. We can use python_CFLAGS. So let's remove the comment about https://bugs.python.org/issue15018.
* Fix python executed during configurej.r2022-02-181-5/+4
| | | | | | | | | | | | | | | 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
* build: use target instead of hostMichael Vetter2022-02-181-3/+3
| | | | | | | If I understand https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Canonicalizing.html correctly then we should use target and not host. Will only matter in case of crosscompiling.
* build: use PKG_CHECK_MODULES to check for xscreensaverMichael Vetter2022-02-181-13/+6
|
* build: use CFLAGS instead of CPPFLAGS where possibleMichael Vetter2022-02-181-6/+6
| | | | OSX seems to need CPPFLAGS for readline.
* build: remove otr3 supportMichael Vetter2022-02-181-14/+8
| | | | All the distributions I checked have libotr 4.1.1 now.
* build: remove support for old libsignalMichael Vetter2022-02-181-8/+1
| | | | | | | | | Remove support for libsignal-protocol-c < 2.3.2. Debian 10 uses 2.3.2, Debian 11 and 12 use 2.3.3. openSUSE from 15.2 onward uses 2.3.3. Fedora since 28 uses 2.3.2. We should be good.
* build: remove xmpp_lib variableMichael Vetter2022-02-181-4/+3
| | | | | Since cad934b9a069bb2c3c417d4efc64dc25fb9814b7 we only support libstrophe. libmesode is deprecated.
* build: group related parts better togetherMichael Vetter2022-02-181-49/+58
|
* build: change commentsMichael Vetter2022-02-181-28/+30
|
* build: define min autotools version and set urlMichael Vetter2022-02-181-2/+3
|
* build: use AC_MSG_NOTICE instead of echoMichael Vetter2022-02-181-14/+15
|
* build: add vim modelineMichael Vetter2022-02-171-1/+2
|
* 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
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-26 07:44:09 +0000