This section applies only to building code which has been checked out of the CVS repository. It does not apply to building a distribution tarball: that process is nothing more than the usual:
with the usual options for the% ./configure % make % make install
./configure
script, of which the most important is --prefix
to control the installation location of the code. The default
location is typically /star, though a particular
distribution might have a different value (see
./configure --help for more details).Recall that the make install, above, installs a
manifest listing the files actually installed, in the directory
/star/manifests (depending on the value of
--prefix, which defaults to the value shown by
./starconf.status --show STARCONF_DEFAULT_PREFIX).
Most users of this document will likely be concerned only with the details of building a particular component, and thus concerned primarily with Section 3.3.
Only rather few users are concerned with building the entire tree, for example for the nightly build: this is dealt with in Section 3.2.
Note: In all cases, you should not
have the INSTALL environment variable defined.
In old-style Starlink makefiles this indicated the install
location; in the new-style build system, this location is
indicated by the `prefix' described above abd elsewhere, and
the generated Makefiles take the INSTALL variable
to be the name of a program to use to perform the actual
installation.