to teem

Directory Structure

teem

THIS IS UNFINISHED

Directory structure: Upon unpacking a tarball, or doing a "cvs checkout", there will be a directory named something like teem. It contains:
LICENSE.txt Any code written here at the U of U is bound by this license, whether we like it or not.
README.txt General pleasantries.
include/ This is where the header files are put upon doing a "make install" of a library, and it is the single place that other libraries (including teem libraries) should look for any teem header files.
irix6.64/
irix6.n32/
linux/
solaris/
This is where any architecture-specific things go. But those aren't architectures, you say, those are operating systems! So, more precisely, the setting of the environment variable TEEM_ARCH will control where "make" puts the object and library files. Assuming that you don't have two machines with the same operating system, which share a file system, and both want to use the same teem tree, but have incompatible architectures, then the current system should work find. Each of these architecture directories contains:
bin/ Stand-alone binaries go here. Not all libraries have associated binaries; but such binaries are usually simple command-line tools which are themselves wrappers around some set of calls into a teem library.
lib/ All the library files (".a", ".sl", etc) go here. This is single place that other programs (including teem executables) should look to link against teem libraries. don't clutter up the src/ directories.
obj/ Object files get put here when building a library, so as to not clutter up the source directory. There is one subdirectory here for each of the teem libraries.
purify/ In case you're using purify, this is a good place to use for the purify cache, where it puts instrumented versions of other libraries.
The architecture-specific directory contain no files initially. Things are put here as a result of running "make".
src/ This is where all the source files and Makefiles are. There is one subdirectory for each teem library, as well as one directory ("make") just for Makefile-related trickery.