All configuration management of HEASOFT will be handled by the HEASARC, including such things as Makefiles and configure scripts. Code revision control is handled via a central Git repository resident on HEASARC servers. Currently only developers with NASA/GSFC credentials may access this server.
The directory structure for any given subpackage will be reasonably flexible so that mission software developers can arrange things to suit their own needs and/or preferences. Certain constraints may, however, be required to accomodate the overall HEADAS build paradigm.
Full, top-down builds are started from the heasoft/BUILD_DIR directory using the typical GNU-based steps of './configure' followed by 'make' and then finally 'make install'. Internally, however, builds will be managed by the HEASARC's 'hmake' utility. 'hmake' is designed to also make it easy to build all or part of the distribution on any supported platform without having to make modifications by hand specifying the location and/or names of necessary flags and libraries. Before using hmake, one simply needs to initialize HEASOFT by sourcing the file $HEADAS/BUILD_DIR/headas-init.csh (or .sh), where $HEADAS is the environment variable which points to the location of the relevant HEASOFT installation, e.g. /usr/local/heasoft/x86_64-pc-linux-gnu-libc2.12.