The CTEST interface requires users to specify the location of include
files. SRT discovers them by searching through ., src, include, .
Standalone CTBUILD copies these files to installation directory.
External dependencies
Installed binaries and the results of component and integrated tests
depend on the objects and libraries in other packages. Should the
former be marked for rebuild when the latter are modified? CTBUILD
presently does this.
Organization of the installation directory
SRT first divides the release are by target (bin, lib, tmp) and then by
architecture. If we reverse this (e.g. $BFARCH/lib instead of
lib/$BFARCH then the installation for any one architecture is completely
self contained.
CTBUILD allows user to specify either.
Architecture-dependent definitions
CTBUILD provides a mechanism to assign values for a
collection of architecture-dependent variables.
Is the collection sufficient for our spctrum of architectiures
(compilers and operating systems)?