- -------------------------
- strongSwan - Development
- -------------------------
+ ------------------------
+ strongSwan - Development
+ ------------------------
-For interested developers, we have a public repository. To check out and
-compile the code, you need the following tools:
+Git repository
+---------------------
- - Subversion (1.3.1)
- - a recent GNU C complier (gcc-3.4.6)
- - recent autotools (autoconf-2.59, automake-1.9.6, libtool-1.5.22)
- - the usual strongSwan dependencies (gmp >= 4.1.4, optional curl, ldap)
- - perl (5.8.8)
- - lex (flex-2.5.33)
- - yacc (bison-2.1)
- - gperf (3.0.1)
- - Doxygen (1.4.6)
+For interested developers, we have a public repository. To check out and compile
+the code, you need the following tools:
-The numbers in brackets represent the versions used on our development systems,
-other version MAY work, too. Not all tools are checked by the configure script,
-as they are not needed in the tarball distributions, so check them manually.
+ - Git
+ - a recent GNU C compiler (>= 3.x)
+ - automake
+ - autoconf
+ - libtool
+ - pkg-config
+ - gettext
+ - perl
+ - python
+ - lex/flex
+ - yacc/bison
+ - gperf
-To check out the trunk, use:
+ Optionally:
+ - lcov/genhtml
+ - Doxygen
- svn co http://www.strongswan.org/ikev2/trunk strongswan
+To check out the master branch, use:
+
+ git clone git://git.strongswan.org/strongswan.git
+
+or using HTTP:
+
+ git clone https://git.strongswan.org/strongswan.git
After a successful check out, give the autotools a try:
./configure [options]
make
make install
+
+
+API documentation
+-----------------
+
+Charon and libstrongswan contain inline code documentation. These comments can
+be extracted using doxygen. It is built using 'make apidoc', which creates an
+'apidoc' folder containing the HTML files.
+
+strongSwan wiki
+---------------
+
+A wiki for users and developers, including ticket system and source browser
+is available at
+
+ https://wiki.strongswan.org
+