On Wed, 28 Aug 2002, Thomas Goddard wrote:
I think the Chimera build system should not install Chimera as each piece is built. The trouble with that is if the build fails half way through, then the installed Chimera is crippled. I don't want that to happen even on our development machines. I think Chimera should build into a temporary build directory, and when the build succeeds, a "make install" puts it in the installed location. This is an easy change to our current system, simply pointing the Chimera build to a temporary directory instead of the install directory.
Actually we have such a two-stage system for the PCs, it's called ryle. I'm thinking of modifying the installer so it won't run on ryle. As for the other systems, we already have the equivalent of a temporary build directory, the source/obj directory where the code is built. Chimera can use that version very easily (with --pypath) without overwriting the installed version and "make install" behaves as described. Perhaps a little more restraint on the part of developers to wait until after testing their changes to install them is needed (myself included). Greg