GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: Mention language bindings in the manual.

Browse Source 
--

Signed-off-by: Werner Koch <wk@gnupg.org>
This commit is contained in:
Werner Koch 2016-09-19 09:06:24 +02:00
parent 9d62bacac7
commit db23985127
No known key found for this signature in database
GPG Key ID: E3FDFF218E45B72B
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/gpgme.texi
View File

@ -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 examples at the end of the manual, and then only read up those parts
of the interface which are unclear. 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 @node Features
@section 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 integrate strong cryptography in his application. Once support for
@acronym{GPGME} has been added to a program, it is easy to add support @acronym{GPGME} has been added to a program, it is easy to add support
for other crypto protocols once @acronym{GPGME} backends provide them. 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 @node Overview
@section Overview @section Overview