4 >Global Config File
</TITLE
7 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.44"><LINK
10 HREF=
"book1.html"><LINK
12 TITLE=
"Customizing DejaGnu"
13 HREF=
"customizing.html"><LINK
15 TITLE=
"Customizing DejaGnu"
16 HREF=
"customizing.html"><LINK
18 TITLE=
"Board Config File"
19 HREF=
"boardconfig.html"></HEAD
32 >DejaGnu: The GNU Testing Framework
</TH
40 HREF=
"customizing.html"
47 >Chapter
3. Customizing DejaGnu
</TD
53 HREF=
"boardconfig.html"
67 >Global Config File
</A
70 >The master config file is where all the target specific
71 config variables get set for a whole site get set. The idea is
72 that for a centralized testing lab where people have to share a
73 target between multiple developers. There are settings for both
74 remote targets and remote hosts. Here's an example of a Master
75 Config File (also called the Global config file) for a
79 >. A canadian cross is when
80 you build and test a cross compiler on a machine other than the
81 one it's to be hosted on.
</P
83 >Here we have the config settings for our California
84 office. Note that all config values are site dependant. Here we
85 have two sets of values that we use for testing m68k-aout cross
86 compilers. As both of these target boards has a different
87 debugging protocol, we test on both of them in sequence.
</P
92 >Example
3-
4. Global Config file
</B
101 CLASS=
"PROGRAMLISTING"
102 > # Make sure we look in the right place for the board description files.
103 if ![info exists boards_dir] {
106 lappend boards_dir
"/nfs/cygint/s1/cygnus/dejagnu/boards"
108 verbose
"Global Config File: target_triplet is $target_triplet" 2
111 case
"$target_triplet" in {
113 set target_list
"unix"
116 set target_list
"sparc64-sim"
119 set target_list
"mips-sim wilma barney"
122 set target_list
"mips-lsi-sim{,soft-float,el}"
125 set target_list {
"sh-hms-sim" "bloozy" }
134 >In this case, we have support for several cross compilers,
135 that all run on this host. For testing on operating systems that
136 don't support Expect, DejaGnu can be run on the local build
137 machine, and it can connect to the remote host and run all the
138 tests for this cross compiler on that host. All the remote OS
139 requires is a working telnetd.
</P
141 >As you can see, all one does is set the variable
145 > to the list of targets and options to
146 test. The simple settings, like for
150 > only require setting the name of
151 the single board config file. The
<I
155 target is more complicated. Here it sets the list to three target
156 boards. One is the default mips target, and both
164 symbolic names for other mips boards. Symbolic names are covered
168 >Adding A New Board
</I
170 > chapter. The more complicated
171 example is the one for
<I
175 runs the tests with multiple iterations using all possible
176 combinations of the
<TT
183 > (little endian) option. Needless to say,
184 this last feature is mostly compiler specific.
</P
201 HREF=
"customizing.html"
217 HREF=
"boardconfig.html"
226 >Customizing DejaGnu
</TD
232 HREF=
"customizing.html"
239 >Board Config File
</TD