aboutsummaryrefslogtreecommitdiffstats
path: root/lang/python/docs/GPGMEpythonHOWTOen.org
diff options
context:
space:
mode:
authorBen McGinnes <[email protected]>2018-03-15 16:52:58 +0000
committerBen McGinnes <[email protected]>2018-03-15 16:52:58 +0000
commit431897a4c48fe1bc9d37f655097aabaf5b685d11 (patch)
treead40322aa0d0698b842405b3769975ebec9a9e05 /lang/python/docs/GPGMEpythonHOWTOen.org
parentdoc: python bindings howto (diff)
downloadgpgme-431897a4c48fe1bc9d37f655097aabaf5b685d11.tar.gz
gpgme-431897a4c48fe1bc9d37f655097aabaf5b685d11.zip
doc: python bindings howto
* Added clarification on why it's not on PyPI.
Diffstat (limited to 'lang/python/docs/GPGMEpythonHOWTOen.org')
-rw-r--r--lang/python/docs/GPGMEpythonHOWTOen.org8
1 files changed, 8 insertions, 0 deletions
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