DejaGnu: The GNU Testing Framework
<<< Previous | Customizing DejaGnu | Next >>>

# Global Config File

The master config file is where all the target specific config variables for a whole site get set. The idea is that for a centralized testing lab where people have to share a target between multiple developers. There are settings for both remote targets and remote hosts. Here's an example of a Master Config File (also called the Global config file) for a canadian cross. A canadian cross is when you build and test a cross compiler on a machine other than the one it's to be hosted on.

Here we have the config settings for our California office. Note that all config values are site dependant. Here we have two sets of values that we use for testing m68k-aout cross compilers. As both of these target boards has a different debugging protocol, we test on both of them in sequence.

Example 4. Global Config file

          # Make sure we look in the right place for the board description files.
          if ![info exists boards_dir] {
              set boards_dir {}
          }
          lappend boards_dir "/nfs/cygint/s1/cygnus/dejagnu/boards"

          verbose "Global Config File: target_triplet is $target_triplet" 2
          global target_list

          case "$target_triplet" in {
              { "native" } {
                  set target_list "unix"
              }
              { "sparc64-*elf" } {
                  set target_list "sparc64-sim"
              }
              { "mips-*elf" } {
                  set target_list "mips-sim wilma barney"
              }
              { "mips-lsi-elf" } {
                  set target_list "mips-lsi-sim{,soft-float,el}"
              }
              { "sh-*hms" } {
                  set target_list { "sh-hms-sim" "bloozy" }
              }
          }

In this case, we have support for several cross compilers, that all run on this host. For testing on operating systems that don't support Expect, DejaGnu can be run on the local build machine, and it can connect to the remote host and run all the tests for this cross compiler on that host. All the remote OS requires is a working telnetd.

As you can see, all one does is set the variable target_list to the list of targets and options to test. The simple settings, like for sparc64-elf only require setting the name of the single board config file. The mips-elf target is more complicated. Here it sets the list to three target boards. One is the default mips target, and both wilma barney are symbolic names for other mips boards. Symbolic names are covered in the Adding A New Board chapter. The more complicated example is the one for mips-lsi-elf. This one runs the tests with multiple iterations using all possible combinations of the `--soft-float` and the `--el` (little endian) option. Needless to say, this last feature is mostly compiler specific.

<<< Previous | Home | Next >>>
Customizing DejaGnu | Up | Board Config File