gpgme/configure.ac, branch gpgme-1.21.0GnuPG Made Easy.http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.21.02023-07-07T11:35:14ZRelease 1.21.02023-07-07T11:35:14ZWerner Kochwk@gnupg.org2023-07-07T11:33:25Zurn:sha1:5bf3e6d0754a179b316f90a885371af99bc03ea1Fix definition of GPG_ERR_ENABLE_GETTEXT_MACROS2023-06-13T10:45:08ZAndre Heineckeaheinecke@gnupg.org2023-06-13T10:45:08Zurn:sha1:7e6d51aa6fc97bed12486540167e9b710c9a3378
* configure.ac: Add missing value.
--
Otherwise it would not be included in config.h
Post release updates2023-04-20T12:02:34ZWerner Kochwk@gnupg.org2023-04-20T12:02:34Zurn:sha1:d99156ff081c08cf83c437bdae85a1f2c3b4f020
--
Release 1.20.02023-04-20T11:48:17ZWerner Kochwk@gnupg.org2023-04-20T11:48:17Zurn:sha1:451ed47434c5ffd2916adae25e5a128606b5ef98w32: Always use UTF-8 for localized texts2023-04-04T10:11:15ZIngo Klöckerdev@ingo-kloecker.de2023-04-04T10:11:15Zurn:sha1:d256ba7cc57d9bfcfa05fb05cf66dc992efbb695
* configure.ac: Define GPG_ERR_ENABLE_GETTEXT_MACROS.
* src/version.c (do_subsystem_inits) [W32]: Switch gettext to UTF-8.
--
On Windows, applications using GpgME can now rely on localized texts
returned by GpgME, e.g. the texts for error codes, to be UTF-8 encoded.
In particular, this saves a useless and possibly lossy conversion to
native encoding and back to UTF-8. On other OSes, where we use the
system provided gettext, we assume that UTF-8 is used nowadays.
GnuPG-bug-id: 5960
Post release updates2023-03-17T10:42:33ZWerner Kochwk@gnupg.org2023-03-17T10:42:33Zurn:sha1:18e09b15d58d9ce13d997967b5ba0a32b3efc828
--
Release 1.19.02023-03-17T09:34:42ZWerner Kochwk@gnupg.org2023-03-17T09:34:42Zurn:sha1:96a30fdf30626a7cefd9c9e620a60817ef44fde2python: Update python.m4 configure script.2023-03-17T09:06:55ZBen Greiner (bnavigator)unknown@dev.gnupg.org2023-03-16T14:09:38Zurn:sha1:d086653cc346d5634bc742d5586e927fc9ee57cf
* configure.ac: Unset PYTHON_LIBS. Support python 3.10.
* m4/python.m4: Find correct version string for python >= 3.10.
--
See-also: https://dev.gnupg.org/D546
Also test for 3.11 and 3.12 (wk).
Update NEWS and set version to 1.19.02023-01-31T07:10:29ZWerner Kochwk@gnupg.org2023-01-31T07:10:29Zurn:sha1:577562dd4cabea53e5119f609eecf666ba84dc46
--
build,qt: Allow building QGpgME for Qt 62022-10-11T09:00:14ZIngo Klöckerdev@ingo-kloecker.de2022-10-11T08:14:53Zurn:sha1:8d019bbb8d40de2cbed7ad6d3367c6a46a561fab
* configure.ac: Look for Qt 5 and/or Qt 6. Require C++17 if Qt 6 binding
is built. Build cmake files QGpgmeConfig* for Qt 5 and QGpgmeQt6Config*
for Qt 6.
(available_languages): Add "qt5" and "qt6".
(WANT_QT5, WANT_QT6): New conditionals.
* lang/qt/src/Makefile.am: Keep building libqgpgme for Qt 5. Build
libqgpgmeqt6 for Qt 6.
* lang/qt/tests/Makefile.am: Build tests for Qt 5 or Qt 6.
* lang/qt/src/QGpgmeQt6Config-w32.cmake.in.in,
lang/qt/src/QGpgmeQt6Config.cmake.in.in,
lang/qt/src/QGpgmeQt6ConfigVersion.cmake.in, m4/qt6.m4: New.
--
This makes it possible to build QGpgME optionally for Qt 6.4.0 or later.
By default or if the language "qt" is enabled, then QGpgME is built
either for Qt 5 (if found) or Qt 6. A build for Qt 5 or Qt 6 can be
requested by explicitly enabling the language "qt5" or "qt6". Building
QGpgME for Qt 5 and Qt 6 simultaneously is not supported.