1
# $Id: README-CVS,v 1.3 2001/04/26 13:44:37 zeller Exp $
2
# Getting DDD from the public CVS Archive
4
DDD now has a public CVS archive (hosted at SourceForge) where you can
5
download arbitrary DDD releases (typically the latest one). Using
6
your local CVS version, you can always download the latest changes and
7
thus stay in sync with DDD development.
9
To checkout and build DDD from the public CVS archive, follow these steps:
11
1. Check the DDD repository for latest news. Go to:
13
http://sourceforge.net/projects/ddd/
16
2. Check your prerequisites.
18
The CVS repository does not contain derived files, only DDD
19
sources. Hence, you need several tools on your local machine for
22
A list of the most important tools can be found in the DDD
23
`INSTALL' file, as `tools you need if you make changes to the DDD
24
sources'. All these tools are required.
27
3. Checkout DDD. Use these commands:
29
$ cvs -d:pserver:anonymous@cvs.ddd.sourceforge.net:/cvsroot/ddd login
31
If you are prompted for a password, just hit Enter.
33
$ cvs -z3 -d:pserver:anonymous@cvs.ddd.sourceforge.net:/cvsroot/ddd \
36
This creates a `ddd/' subdirectory containing all DDD code.
38
The `-kkv' option is required to expand RCS keywords, thus allowing
39
prompt version identification. `-z3' enables compression.
42
4. After successful checkout, have a look at `ddd/README-CVS' for the
43
most recent version of this document.
46
5. Setup the distribution. DDD includes a `CVSMake' script that does
47
the job for you. Change to the DDD top-level directory
55
Messages about missing `.in' or `ChangeLog' files can be safely ignored.
57
Note: You may require special tools to setup the distribution,
58
including `automake', `aclocal', `flex', `bison' and `makeinfo'.
59
If `CVSMake' fails at some point, install the necessary package and
60
simply run `CVSMake' again.
62
Note: running `CVSMake' takes some time.
65
6. If all went well, you can now re-configure, build, and install DDD
66
as described in the `INSTALL' file. Example commands:
73
7. `CVSMake' and `make', as described above, do not generate formatted
74
documentation (i.e. PDF and HTML files). It is suggested that you
75
use formatted documentation from the DDD distributions.
77
However, you can create formatted documentation from source. For
78
this, you need several typesetting and graphics tools, such as
79
LaTeX, PDFLaTeX, netpbm, pbmplus, ... The `INSTALL' file has a list.
81
To create formatted documentation from source, type
86
8. You can always sync with the current development state by using
90
and rebuild DDD using `make'.
added
removed
README-CVS
