estreams symbols for python bindings
* It turns out that even though some platforms detect differing symbols for estreams, the two types do not appear to be in conflict. At least they don't from the BSD/OS X side of things. As a consequence both versions are now included. Tested-by: Ben McGinnes <ben@adversary.org> Signed-off-by: Ben McGinnes <ben@adversary.org>
This commit is contained in:
parent
dacb119715
commit
879cc1f84f
@ -272,7 +272,8 @@ EXPORTS
|
|||||||
gpgme_op_encrypt_sign_ext @202
|
gpgme_op_encrypt_sign_ext @202
|
||||||
gpgme_op_encrypt_sign_ext_start @203
|
gpgme_op_encrypt_sign_ext_start @203
|
||||||
|
|
||||||
_gpgme_data_new_from_estream @204
|
gpgme_data_new_from_estream @204
|
||||||
|
_gpgme_data_new_from_estream @205
|
||||||
|
|
||||||
; END
|
; END
|
||||||
|
|
||||||
|
@ -134,6 +134,7 @@ GPGME_1.1 {
|
|||||||
gpgme_op_decrypt_ext;
|
gpgme_op_decrypt_ext;
|
||||||
gpgme_op_decrypt_ext_start;
|
gpgme_op_decrypt_ext_start;
|
||||||
|
|
||||||
|
gpgme_data_new_from_estream;
|
||||||
_gpgme_data_new_from_estream;
|
_gpgme_data_new_from_estream;
|
||||||
|
|
||||||
};
|
};
|
||||||
|
Loading…
Reference in New Issue
Block a user