Libassuan
                             ===========

    Copyright (C) 2001-2013 Free Software Foundation, Inc.
    Copyright (C) 2001-2021 g10 Code GmbH


    This is a general purpose IPC library which is for example used
    GnuPG, GPGME and some other software.

    See COPYING.LIB on how to share, modify and distribute the
    software itself (LGPLv2.1+) and COPYING for the documentation
    (GPLv3+).

    Please send bug report to the gnupg-devel mailing list or enter
    them into the gnupg bug tracker at https://bugs.gnupg.org using the
    category "libassuan".

    The primary FTP site is https://gnupg.org/ftp/gcrypt/libassuan.


    Notes for Windows CE:
    ----------------------

    Libassuan supports WindowsCE (tested with WindowsMobile 6.5).  To
    install it, copy libassuan-0.dll into a location where DLL are found
    and install the included gpgcedev driver: First copy "gpgcedev.dll"
    into the root directory, second run the included program gpgcemgr on
    the device: "gpgcemgr --register".  This creates the necessary
    registry keys.  In case the copy step fails, the driver may still be
    in use: Close all applications using that driver, run "gpgcemgr
    --deactivate" to deactivate the running driver and try again.

    Registry keys created by "gpgcemgr --register" are:

       Drivers\\GnuPG_Device\dll    -> "gpgcedev.dll"
       Drivers\\GnuPG_Device\prefix -> "GPG"
       Drivers\\GnuPG_Device\Index  -> 1      (dword)


    Contact
    -------

    See the file AUTHORS.

    Commercial grade support for Libassuan and GnuPG is available; for
    a listing of offers see https://www.gnupg.org/service.html .
    Maintaining and improving this software is costly.  Since 2001,
    g10 Code GmbH, a German company owned and headed by GnuPG's
    principal author Werner Koch, is bearing the majority of these
    costs.  To help them carry on this work, they need your support.
    See https://gnupg.org/donate/ .

If you are building from GIT, run the script

./autogen.sh

first, to make sure that you have all the necessary maintainer tools
are installed and to build the actual configuration files.  If you
have just checked out from GIT, you should add the option "--force" to
autogen.sh so that meta data is noticed by autom4te.cache.  Then run

./configure --enable-maintainer-mode

followed by the usual make.

If autogen.sh complains about insufficient versions of the required
tools, or the tools are not installed, you may use environment
variables to override the default tool names:

 AUTOMAKE_SUFFIX  is used as a suffix for all tools from the automake
                  package.  For example
                     AUTOMAKE_SUFFIX="-1.7" ./autogen.sh
                  uses "automake-1.7" and "aclocal-1.7.
 AUTOMAKE_PREFIX  is used as a prefix for all tools from the automake
                  page and may be combined with AUTOMAKE_SUFFIX. e.g.:
                    AUTOMAKE_PREFIX=/usr/foo/bin ./autogen.sh
                  uses "automake" and "aclocal" in the /usr/foo/bin
                  directory.
 AUTOCONF_SUFFIX  is used as a suffix for all tools from the automake
                  package
 AUTOCONF_PREFIX  is used as a prefix for all tools from the automake
                  package
 GETTEXT_SUFFIX   is used as a suffix for all tools from the gettext
                  package
 GETTEXT_PREFIX   is used as a prefix for all tools from the gettext
                  package

It is also possible to use the variable name AUTOMAKE, AUTOCONF,
ACLOCAL, AUTOHEADER, GETTEXT and MSGMERGE to directly specify the name
of the programs to run.  It is however better to use the suffix and
prefix forms as described above because that does not require
knowledge about the actual tools used by autogen.sh.


Please don't use autopoint, libtoolize or autoreconf unless you are
the current maintainer and want to update the standard configuration
files.  All those files should be in GIT and only updated manually
if the maintainer decides that newer versions are required.  The
maintainer should also make sure that the required version of automake
et al. are properly indicated at the top of configure.ac and take care
to copy the files and not merely use symlinks.