[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DDD vxworks extension

From: Andreas Zeller
Subject: Re: DDD vxworks extension
Date: 22 Nov 2000 16:28:11 +0100
User-agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands)

"Cliff, Gary" <address@hidden> writes:

> Attached is a tar file containing the modified files (from version
> 3.2.90)  and a readme file for vxworks to explain how to
> integrate DDD into Tornado [...].
> Could you be so kind to tell me when you've had a chance to put this
> into a release?

Thanks!  This will go into the DDD 3.2.92 release, due in the next few days.

> (Is there some way you could put this is some sort of test release first
> which I could download and test out here to make sure I haven't missed
> anything?)

Well, DDD 3.2.92 is already a test release.  If this is still `too
official' for you, you can download the most recent DDD version
straight from its CVS archive.  

Note that I do not recommend _building_ from the CVS archive version -
you'd need several uncommon tools for that.  However, you can easily
examine the CVS version and check the differences.  For instance, you
can copy any modified files back into your own version.

Thanks again, and have a nice Thanksgiving weekend,


# $Id: README-CVS,v 1.1 2000/07/20 09:31:04 zeller Exp $
# Getting DDD from the public CVS Archive

DDD now has a public CVS archive (hosted at SourceForge) where you can
download arbitrary DDD releases (typically the latest one).  Using
your local CVS version, you can always download the latest changes and
thus stay in sync with DDD development.

To checkout and build DDD from the public CVS archive, follow these steps:

1. Check the DDD repository for latest news.  Go to:


2. Check your prerequisites. 

   The CVS repository does not contain derived files, only DDD
   sources.  Hence, you need several tools on your local machine for
   building DDD.

   A list of the most important tools can be found in the DDD
   `INSTALL' file, as `tools you need if you make changes to the DDD
   sources'.  All these tools are required.

3. Checkout DDD.  Use these commands:

   $ cvs -d:pserver:address@hidden:/cvsroot/ddd login
   $ cvs -z3 -d:pserver:address@hidden:/cvsroot/ddd \
     checkout -kkv ddd

   This creates a `ddd/' subdirectory containing all DDD code.

   The `-kkv' option is required to expand RCS keywords, thus allowing
   prompt version identification.  `-z3' enables compression.

4. After successful checkout, have a look at `ddd/README-CVS' for the
   most recent version of this document.

5. Setup configuration files.  Use these commands:

   $ (cd ddd && aclocal)
   $ autoconf -l ddd
   $ automake --gnu --add-missing --copy --verbose
   $ (cd ddd && autoconf && automake --foreign --add-missing --copy --verbose)
   $ (cd vsllib && autoconf -l ../ddd && automake --foreign --verbose)
   $ (cd themes && autoconf -l ../ddd && automake --foreign --verbose)
   $ (cd readline && autoconf)
   $ (cd termcap && autoconf)

6. Configure DDD, as described in the `INSTALL' file.  Example command:

   $ sh ./configure

7. Build libraries.  Use these commands:

   $ (cd libiberty && test -f Makefile && make)
   $ (cd termcap   && test -f Makefile && make)
   $ (cd readline  && test -f Makefile && make)

8. Setup DDD Makefiles.  Use these commands:

   $ cd ddd
   $ make Makefile
   $ make Makefile

9. Create DDD precompiled files (including documentation).  Still in
   the `ddd' directory, use this command:

   $ make diststuff

   If any command is missing, install it and try again.

10. You're done!  You can now re-configure, build, and install DDD as described
   in the `INSTALL' file.  Example commands:

   $ cd ..
   $ make
   $ make check

11. You can always sync with the current development state by using

   $ cvs update

Andreas Zeller     Universitaet Passau

reply via email to

[Prev in Thread] Current Thread [Next in Thread]