From: Marcus Brinkmann Date: Fri, 23 Nov 2001 01:12:04 +0000 (+0000) Subject: Explain more of the build system. X-Git-Tag: gpgme-1.2.0@1385~1243 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=4d8a8ff411b972fa0355c54430ae60313a1b8716;p=gpgme.git Explain more of the build system. --- diff --git a/trunk/README b/trunk/README index cf58777..55c40f5 100644 --- a/trunk/README +++ b/trunk/README @@ -3,23 +3,36 @@ !!!! THIS IS WORK IN PROGRESS !!! -If you want to hack on it, start with one of the tests/t-foo programs. -You need the latest CVS version of GnuPG 1.0, see -http://www.gnupg.org/cvs-access.html . +If you want to hack on it, start with one of the `tests/t-foo' +programs. -You need at least GnuPG 1.0.6 (but don't use a 1.1.x version). +For support of the OpenPGP protocol (default), you need the latest CVS +version of GnuPG 1.0, see `http://www.gnupg.org/cvs-access.html'. +You need at least GnuPG 1.0.6, but don't use a 1.1.x version. -To build the W32 version, use -./autogen.sh --build-w32 +If configure can't find the `gpg' binary in your path, you can specify +the location with the --with-gpg=/path/to/gpg argument to configure. +For support of the CMS (Cryptographic Message Syntax) protocol, you +need the latest CVS version of GpgSM, module name `newpg' at +`:pserver:anoncvs@cvs.gnupg.org:/cvs/aegypten'. -Please subscribe to the gnupg-devel@gnupg.org mailing list if you want -to do serious work. +If configure can't find the `gpgsm' binary in your path, you can +specify the location with the --with-gpgsm=/path/to/gpgsm argument to +configure. + +To enable the CryptPlug GPGME PlugIn for both protocols, use the +`--enable-gpgmeplug' option to the configure script. `gpgmeplug' is +experimental and you should not assume that it will stay with gpgme. +Before building the CVS version following the generic install +instructions in `INSTALL', you need to set up the build scripts with +`./autogen.sh'. To build the W32 version, use `./autogen.sh +--build-w32'. -gpgmeplug/ is experimental and you should not assume that it will stay -with gpgme. +Please subscribe to the gnupg-devel@gnupg.org mailing list if you want +to do serious work.