diff options
author | Werner Koch <[email protected]> | 2016-09-19 07:06:24 +0000 |
---|---|---|
committer | Werner Koch <[email protected]> | 2016-09-19 07:06:32 +0000 |
commit | db2398512796f28f0f92e32e0de3180d93f76a26 (patch) | |
tree | bf42a0ea518e8292b13e2524b78433892446aaa5 | |
parent | core: Check for GPG_TTY as well as DISPLAY. (diff) | |
download | gpgme-db2398512796f28f0f92e32e0de3180d93f76a26.tar.gz gpgme-db2398512796f28f0f92e32e0de3180d93f76a26.zip |
doc: Mention language bindings in the manual.
--
Signed-off-by: Werner Koch <[email protected]>
-rw-r--r-- | doc/gpgme.texi | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/doc/gpgme.texi b/doc/gpgme.texi index 18fb6d5c..ec7ebb77 100644 --- a/doc/gpgme.texi +++ b/doc/gpgme.texi @@ -298,6 +298,13 @@ library. Experienced programmers might want to start looking at the examples at the end of the manual, and then only read up those parts of the interface which are unclear. +The documentation for the language bindings is currently not included +in this manual. Those languages bindings follow the general +programming model of @acronym{GPGME} but may provide some extra high +level abstraction on top of the @acronym{GPGME} style API. For now +please see the README files in the @file{lang/} directory of the +source distribution. + @node Features @section Features @@ -324,8 +331,11 @@ the programmer can focus on the other parts of the program, and still integrate strong cryptography in his application. Once support for @acronym{GPGME} has been added to a program, it is easy to add support for other crypto protocols once @acronym{GPGME} backends provide them. -@end table +@item it's language friendly +@acronym{GPGME} comes with languages bindings for several common +programming languages: Common Lisp, C++, Python 2, and Python 3. +@end table @node Overview @section Overview |