Chapter 2. Building And Installing


"It says the the best drink in existence is the Pan Galactic Gargle Blaster. It says that the effect of drinking a Pan Galactic Gargle Blaster is like having your brains smashed out by a slice of lemon wrapped round a large gold brick."

 Douglas Adams
Table of Contents
Getting The Sources
Building The PDEPP Webserver
Testing The PDEPP Webserver

Getting The Sources

Getting Source Tarballs

Getting a prepared source release is probably the preferable way to try the PDEPP Webserver as you will at least get a version that does compile - that is, chances that it will at least compile are better than with sources checked out of CVS. ;-)

Source releases can be found at PDEPP Webserver's Website. It's probably a good idea to fetch the latest release available.

Getting Sources From CVS

Another way - and, until not too long ago the only way - to try the PDEPP Webserver is to check the sources out of CVS and compile it yourself. To check out the sources you need a CVS client installed.

You can check the sources out anonymously by doing the following:

  • cvs login

    (Simply hit Enter if asked for a password.)

  • cvs -z3 co pdeppd

  • cd pdeppd

  • make -f Makefile.dist

    (You'll need the automake and autoconf packages installed for this to work.)

Creating The Documentation

As PDEPP Webserver's documentation is generated automatically from templates and the source code itself, it is not contained in the CVS repository. To rebuild the complete documentation you'll need the DocBook SGML DTD 4.1, the modular DocBook DSSSL Stylesheets, an DSSSL-processor like jade or openjade (in order to create PDepp's user and administrator manual) and a recent version of doxygen (in order to create the programmers reference manual).

Creating the documentation currently is a very manual process, just run doxygen on PDEPP Webserver's toplevel directory after running configure and use jade to transform the user manual's SGML sources into your favourite format.

Alternatively you can download one of the source tarballs, of course, which come with the documentation already generated / preprocessed.