Next Up Previous Contents
Next: A.22 STAR_MESSGEN
Up: A The Starconf macros and variables
Previous: A.20 STAR_LATEX_DOCUMENTATION
[ID index][Keyword index]

A.21 Variable STAR_MANIFEST_DIR

The STAR_MANIFEST_DIR substitution variable is slightly special. If it is defined in your configure.ac file, then Starlink automake will include in the generated Makefile.in code to create and install a manifest of all the files installed.

If you set this variable at installation time:


make STAR_MANIFEST_DIR=/my/special/manifest install
then this overrides the manifest location defaulted at configure time. If the variable is set to be null (make STAR_MANIFEST_DIR= install) then you will suppress the creation and installation of the manifest.

You define it as follows:


: ${STAR_MANIFEST_DIR='$(prefix)/manifests'}
AC_SUBST(STAR_MANIFEST_DIR)
This sets the variable to be $(prefix)/manifests, but allows it to be overridden by a setting of the variable in the environment. Note that is is set to be relative to the value of the $(prefix) makefile variable.

You do not have to set this in general, as this is one of the things that the STAR_DEFAULTS macro (Appendix A.17) takes care of. The only time you need to use this feature is when you are importing a third-party code set into the tree (as described in Section 4.5). In that case, you do not want to specify STAR_DEFAULTS in the configure.ac, but you do need to install a manifest. If there is more than one configure.ac file in the tree, you will have to add this for each one.

See also Appendix A.27.


Next Up Previous Contents
Next: A.22 STAR_MESSGEN
Up: A The Starconf macros and variables
Previous: A.20 STAR_LATEX_DOCUMENTATION
[ID index][Keyword index]
The Starlink Build System
Starlink System Note 78
Norman Gray, Peter W Draper, Mark B Taylor, Steven E Rankin
11 April 2005. Release snapshot: $Revision: 1.116 $. Last updated 28 May 2006