From 431897a4c48fe1bc9d37f655097aabaf5b685d11 Mon Sep 17 00:00:00 2001 From: Ben McGinnes Date: Fri, 16 Mar 2018 03:52:58 +1100 Subject: doc: python bindings howto * Added clarification on why it's not on PyPI. --- lang/python/docs/GPGMEpythonHOWTOen.org | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'lang/python/docs/GPGMEpythonHOWTOen.org') diff --git a/lang/python/docs/GPGMEpythonHOWTOen.org b/lang/python/docs/GPGMEpythonHOWTOen.org index 4aa4398c..28d2e25d 100644 --- a/lang/python/docs/GPGMEpythonHOWTOen.org +++ b/lang/python/docs/GPGMEpythonHOWTOen.org @@ -179,6 +179,14 @@ Due to the nature of what these bindings are and how they work, it is infeasible to install the GPGME Python bindings in the same way. + This is because the bindings use SWIG to dynamically generate C + bindings against =gpgme.h= and =gpgme.h= is generated from + =gpgme.h.in= at compile time when GPGME is built from source. Thus + to include a package in PyPI which actually built correctly would + require either statically built libraries for every architecture + bundled with it or a full implementation of C for each + architecture. + ** Requirements :PROPERTIES: :CUSTOM_ID: gpgme-python-requirements -- cgit v1.2.3