It is usually best to configure in a directory separate
from the source tree, specifying where to find the source with the
optional `--srcdir' option to configure. DejaGnu uses the
GNU autoconf to configure itself. For more info on using
autoconf, read the GNU autoconf manual. To configure, execute the
`configure' program, no other options are required. For an example,
to configure in a seperate tree for objects, execute the configure
script from the source tree like this:
../dejagnu-1.3/configure
DejaGnu doesn't care at config time if it's for testing a native system or a cross system. That is determined at runtime by using the config files.
You may also want to use the configure option `--prefix' to
specify where you want DejaGnu and its supporting code installed. By
default, installation is in subdirectories of `/usr/local', but you
can select any alternate directory altdir by including
`--prefix=altdir' on the configure command line.
(This value is captured in the Makefile variables prefix
and exec_prefix.)
Save for a small number of example tests, the DejaGnu distribution
itself does not include any test suites; these are available separately.
Test suites for the GNU compiler (testing both GCC and G++) and for
the GNU binary utilities are distributed in parallel with the
DejaGnu distribution (but packaged as separate files). The test suite
for the GNU debugger is distributed in parallel with each release
of GDB itself, starting with GDB 4.9. After configuring the top-level
DejaGnu directory, unpack and configure the test directories for the
tools you want to test; then, in each test directory, run make to
build auxiliary programs required by some of the tests.
Go to the first, previous, next, last section, table of contents.