GnuTLS README-alpha -- Information for developers. -*- outline -*- Copyright (C) 2009-2012 Free Software Foundation, Inc. See the end for copying conditions. This file contains instructions for developers and advanced users that want to build from version controlled sources. We require several tools to check out and build the software, including: - Make - Automake (use 1.11.3 or later) - Autoconf - Autogen (use 5.16 or later) - Libtool - Gettext - Texinfo - Tar - Gzip - Texlive & epsf (for PDF manual) - CVS (for gettext autopoint) - GTK-DOC (for API manual) - Git - Perl - Valgrind (optional) - Nettle - Guile - p11-kit - gperf - libtasn1 (optional) - datefudge (optional) - Libidn (optional, for crywrap) - AWK (for make dist, pmccabe2html) - git2cl (for make dist, ChangeLog) - softhsm (for testing smart card support) - dieharder (for testing PRNG) The required software is typically distributed with your operating system, and the instructions for installing them differ. Here are some hints: gNewSense/Debian/Ubuntu: apt-get install git-core autoconf libtool gettext autopoint apt-get install texinfo texlive texlive-generic-recommended texlive-extra-utils apt-get install help2man gtk-doc-tools valgrind apt-get install guile-1.8-dev libtasn1-3-dev apt-get install datefudge libidn11-dev gawk gperf apt-get install softhsm You will sometimes need to install more recent versions of Automake, Nettle, P11-kit and Autogen, which you will need to build from sources. If your system has the recent versions, you could do: apt-get install automake autogen nettle-dev libp11-kit-dev To download the version controlled sources: $ git clone git://gitorious.org/gnutls/gnutls.git $ cd gnutls The next step is to run autoreconf (etc) and then ./configure: $ make bootstrap When built this way, some developer defaults will be enabled. See cfg.mk for details. Then build the project normally: $ make $ make check Individual tests that may require additional hardware (e.g., smart cards) are: $ sh tests/suite/testpkcs11 If you wish to contribute, you may read more about our coding style in doc/README.CODING_STYLE. Note that when contributing code that is not assigned to FSF, you will need to assert that the contribution is in accordance to the "Developer's Certificate of Origin" as found in the file doc/DCO.txt. That can be done by sending a mail with your real name to the gnutls-devel mailing list. Then just make sure that your contributions (patches), contain a "Signed-off-by" line, with your name and e-mail address. To automate the process use "git am -s" to produce patches. Happy hacking! ---------------------------------------------------------------------- Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.