[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    [Kde-pim] Build instructions for the aegypten_branch
From:       Marc Mutz <marc () klaralvdalens-datakonsult ! se>
Date:       2004-02-19 14:40:01
Message-ID: 200402191540.19860.marc () klaralvdalens-datakonsult ! se
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi!

For those interested, here are the CVS build instructions for the 
next-generation KMail crypto support currently under development in the 
aegypten_branch and HEAD.

Preliminaries:
	Qt 3.2.3: preferably from rpm's or TT's tarballs, else qt-copy's branch
	KDE 3.2.0: at least arts, libs, base from release tarballs, or rpm's
	(don't forget the -dev packages when using binary packages)
	GnuPG 1.2.x, x >= 2 (rpm's or 

# repositories:
AEGYPTEN=:pserver:anoncvs@cvs.gnupg.org/cvs/aegypten
GNUPG=:pserver:anoncvs@cvs.gnupg.org/cvs/gnupg
KDE=:pserver:anoncvs@anoncvs.kde.org/home/kde

To check out:

cvs -d $GNUPG co libgpg-error libassuan libgcrypt gpgme
cvs -d $GNUPG co -r GNUPG-1-9-BRANCH gnupg
cvs -d $KDE co -r KDE_3_2_0_RELEASE kdepim
cd kdepim
cvs up -r aegypten_branch doc/kgpgcertmanager libkdenetwork kmail
cvs up -A mimelib certmanager \
   libkdenetwork/{libgpg-error-copy,libgpgme-copy,gpgmepp,qgpgme}
# (don't you just love KDE's monolithic modules? :)

For convenience (I can't remember the build order otherwise ;):

mv {,00_}libgpg-error
mv {,01_}libassuan
mv {,02_}libksba
mv {,03_}libgcrypt
mv gnupg 04_gnupg-1-9-branch
mv {,05_}dirmngr
mv {,06_}pinentry
mv {,07_}gpgme
mv {,08_}kdepim

To build:

for i in 0[0-7]* ; do (
	cd $i
	# if the following line fails due to too old gettext or am/ac, just
	# downgrade the requirements in the configure.ac files.
	# autoconf 2.54, automake 1.7.2 and gettext 0.11.2 (probably unused)
	# work fine here. If your ac/am has suffixes (e.g. automake-1.7,
	# autoconf-2.5x), then call this:
	# AUTOMAKE_SUFFIX=-1.7 AUTOCONF_SUFFIX=-2.5x ./autogen.sh

	./autogen.sh # this is the equivalent of make -f Makefile.cvs

	./configure --enable-maintainer-mode [--prefix, --with-foo-path, ...]
	make
	# this sometimes sporadically fails in gpgme, but not elsewhere
	# (seems harmless so far):
	make check
	su -c "make install"
); done

cd kdepim
make -f Makefile.cvs
./configure --enable-debug=full \
	--enable-warnings [--prefix, --with-foo-path, ...]
make
(cd libkdenetwork; make check) # other subdirs fail to compile or run,
(cd certmanager; make check) # so don't do a global "make check" :/
su -c "make install"

To configure:

Start "eval $(gpg-agent --daemon)" somewhere in startkde (a patch, 
anyone?) - this sets an environment variable GPG_AGENT_INFO used by the 
backend (and kmail) to find the agent. The agent performs the secret 
key operations, so smartcards etc are transparently handled without 
gpg(sm) knowing about it. The user-visible effect of gpg-agent is it's 
bringin up the pinentry dialog (passphrase dialog) and caching the 
passphrase if ~/.gnupg/gpg-agent.conf contains default-cache-ttl 
<secs>). See kmail.kde.org/kmail-pgpmime-howto.html for configure 
options to put into ~/.gnupg/.

To use:

If you are developer, we can hand out a limited number of 
"near-production" S/MIME certificates for testing purposes. To create 
one, use kgpgcertmanager's certificate wizard, enter your details, and 
save the request in a .p10 file. Ask in private mail where to send that 
to. Alternatively, you may import your already existing certificate. 
I'd like to refer to Danimo for details of this.

In KMail, the backends should be detected autmatically. You can then 
choose in the composer which backend to use (Options->Select Crypto 
Module).

You will notice that there are lots of rough edges left to polish, but 
this is work in progress, and most of the aegypten_branch developers 
use the branch's KMail on a day-to-day basis for project mails and 
mailing lists.

Marc

-- 
Marc Mutz -- marc@klaralvdalens-datakonsult.se, mutz@kde.org
Klarälvdalens Datakonsult AB, Platform-independent software solutions

[Attachment #5 (application/pgp-signature)]

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]