gpgme/m4, branch justus/idiomatic-py-0

python: Make Python detection more robust.

2016-06-01T13:33:52Z

Previously, missing Python development packages made configure fail instead of merely disabling the bindings. * configure.ac: Check for 'PYTHON_VERSION'. * m4/ax_python_devel.m4: Make test non-fatal. Signed-off-by: Justus Winter

Cpp: Set -std=c++11 also if CXXCPP is already set

2016-05-24T12:13:52Z

* m4/ax_cxx_compile_stdxx.m4 (AX_CXX_COMPILE_STDCXX): Set CXXCPP if neccessary. -- This fixes the build with scan-build where CXXCPP is already set but does not include stdc++11. While this deviates from the autotools-archive version of the script it does not make sense to me first to check if stdc++11 needs to be set and then not set it.

build: Add python autoconf macro.

2016-05-17T14:34:39Z

* m4/ax_python_devel.m4: New file. Signed-off-by: Justus Winter

Merge branch 'justus/pyme3'

2016-05-17T13:10:28Z

python: Integrate into the build system.

2016-05-11T11:33:05Z

* configure.ac: Make Python bindings configurable, add new Makefile. * lang/python/Makefile.am: New file. * lang/python/setup.py: Integrate into the build system. * m4/ax_pkg_swig.m4: New file from the autoconf archive. * m4/m4_ax_swig_python.m4: Likewise. Signed-off-by: Justus Winter

Cpp: Require c++ 11 if cpp binding requested

2016-04-03T12:46:51Z

* configure.ac: Call ax_cxx_compile_stdcxx * m4/ax_cxx_compile_stdcxx.m4 -- Depending on c++11 is intended to make the port away from Boost easier. The m4 macro was taken from the website mentioned in the License header of the file.

Qt: Add a unit test for qgpgme

2016-04-03T09:48:46Z

* configure.ac: Configure test Makefile. * m4/qt.m4: Look up Qt5Test flags. * lang/qt/tests/t-keylist.cpp: New. Simple keylist check. * lang/qt/tests/Makefile.am: New. General test framework. -- This test mostly checks that it basically compiles / works and adds a test framework.

Add qgpgme as qt language binding

2016-03-08T14:37:10Z

* configure.ac: Add version defines. Check for qt if neccessary. * lang/README: Mention qt * lang/cpp/src/GpgmeppConfig.cmake.in.in: Remove comment. Find qgpgme. * lang/qt/src/Makefile.am: New. Build qgpgme. * lang/qt/README, lang/qt/src/Makefile.am, lang/qt/src/QGpgmeConfig.cmake.in.in, lang/qt/src/QGpgmeConfigVersion.cmake.in, lang/qt/src/dataprovider.cpp, lang/qt/src/dataprovider.h, lang/qt/src/qgpgme_export.h, m4/qt.m4: New. * lang/cpp/src/GpgmeppConfig.cmake.in.in, lang/cpp/src/Makefile.am: Fix generated config file. -- For now this is just the dataprovider which was part of the KF5 Gpgmepp QGpgme variant. This is very thin but a useful class which is used downstream.

build: Implement SYSROOT feature.

2014-10-02T13:57:50Z

* configure.ac: Document SYSROOT. * m4/gpg-error.m4: Update from libgpg-error master. * src/gpgme.m4: Implement SYSROOT stuff.

Fix libtool 2.4.2 to correctly detect .def files.

2013-05-23T18:15:30Z

* build-aux/ltmain.sh (sed_uncomment_deffile): New. (orig_export_symbols): Uncomment def file before testing for EXPORTS. * m4/libtool.m4: Do the same for the generated code. -- The old code was not correct in that it only looked at the first line and puts an EXPORTS keyword in front if missing. Binutils 2.22 accepted a duplicated EXPORTS keyword but at least 2.23.2 is more stringent and bails out without this fix. There is no need to send this upstream. Upstream's git master has a lot of changes including a similar fix for this problems. There are no signs that a libtool 2.4.3 will be released to fix this problem and thus we need to stick to our copy of 2.4.2 along with this patch. Signed-off-by: Werner Koch