Working With Legacy Software

The environment variable settings for a legacy sandbox do not conflict with the current build system. The legacy build system used $G as the location of either a private sandbox or a public work area containing all software. The current build system added the GTO variable to designate where software developed at Brown is installed and G_IMPORT for third party software packages.

Most legacy software development was done in the /research/graphics/tools/linux directory and G was set to it. After setting up a legacy sandbox the directories under $G should be:

  WIN32/                Legacy Windows utilities.
  bin/                  Legacy installed programs.
  lib/                  Legacy installed libraries.
  src/                  Legacy source code checked out from CVS.
  help/                 Legacy help information.
  tools/                Legacy administrative tools.

Software installed using the current system can be in a separate private sandbox designated by the GTO variable. In this case the private sandbox contains:

  install_linux/        Installed copies of Linux software developed at Brown.
  install_WIN32/        Installed copies of Windows software developed at Brown.
  install_OSX/          Installed copies of Windows software developed at Brown.
  common/               The most recent common code checked out from CVS.
  project/              An empty directory for your project code.

See Using Public or Private Programs and Libraries for a detailed overview of the environment variables and directories.