There are several permutations of variations in building the Cygnus Support Developer's Kit. In this section we try to discuss the majority of the possibilities. Feel free to contact Cygnus Support with any questions or problems.
In these examples, we assume the source code has been extracted from the
tape into `/usr/local/src' on a Sun 4 running SunOS 4.1.3.
Examples are shown using a Bourne-compatible shell (sh,
bash, ksh). Sample command lines which are too long to
fit on the printed page are wrapped as follows:
$ ./configure --prefix=/usr/local/94q4 \
--exec-prefix=/usr/local/94q4/H-sun4 \
--srcdir=/usr/local/src
Such lines are intended to be typed on one single command line.
Examples show a release number of `94q4', and (often) a
hosttype of sun4. In practice, we recommend the values
`progressive-94q4' and `sparc-sun-sunos4.1.3', respectively;
see section How your Developer's Kit was built. The values
are shortened here to make the examples fit on the printed page.
The examples also show the creation of two links. The links aren't necessary, but they do provide an easy way to make your Developer's Kit easily updateable and accessible in a heterogeneous environment.
The first is a link to make updating easier, so that when you upgrade the Developer's Kit you only need to switch that link to bring it online. The second link allows the creation of several toolkits in a heterogeneous network; each different host can have a link to the toolkit configured for the host's architecture and operating system. See section The Heterogeneous Updateable Toolkit.