If you intend to work only on a single component, then you can configure and build it as described in the previous section. As described there, the bootstrapping procedure requires that the `buildsupport' tools -- starconf plus Starlink-specific autotools -- be installed and in your path.
You must install the autotools which are part of the CVS repository, since these have been extended and customised specially for the Starlink build tree (for the details of the differences, see Appendix B). The standard autotools will not work.
The way to do this is to make sure you have the required components checked out (see Section 2.7.2), then go to the top of the tree and give the command
This builds and installs the `buildsupport' tools -- namely the autotools plus starconf -- but does not go on to bootstrap the rest of the tree. The functions of the variables% ./bootstrap --buildsupport
STARCONF_DEFAULT_PREFIX and
STARCONF_DEFAULT_STARLINK were described in
Section 2.2: in order to configure starconf at this
stage, you must define these two variables as environment
variables before running the ./bootstrap
script. This will cause the tools to be installed in the
directory
$STARCONF_DEFAULT_PREFIX/buildsupport/bin, and
the configured starconf to configure components, when it is
itself invoked, so that the default value of
STARCONF_DEFAULT_PREFIX is the value given
here, as described in the previous section.You must use this method of configuring starconf and the three autotools -- autoconf, automake and libtool.
After that, you should put the
.../buildsupport/bin directory in your path,
and start work.
See also Section 2.2.1 for how to make a version of the buildsupport tools which has a default installation prefix different from the buildsupport installation location.