rcbc@honir.cs.cornell.edu (Robert Cooper) (05/08/90)
For the Isis V2.0 release I have changed the Isis binary directory
structure (e.g. the SUN4 directory). I have included a "make install",
"make clean" and "make realclean" targets to the top level makefiles. And
I have changed the names of the library files
The
new structure is mostly compatible with the structure in previous releases.
Better library file names:
The library files are now called
"libisis1.a", "libisis2.a" and "libisism.a" instead of the previous
names lib1.a lib2.a and mlib.a. These are better names for putting
the library files in /usr/local/lib for instance, and allow you to
link with the options "-lisis1 -lisis2 -lisism".
Symbolic links from the old names to the new names are provided
in the "clib" and "mlib" subdirectories for compatibility.
make install:
All binary executables and library files are built in the appropriate
subdirectories, e.g. SUN4/protos/protos, SUN4/util/isis,
SUN4/demos/grid, and SUN4/clib/libisis1.a.
Typing "make install" in the binary directory (e.g. in SUN4) copies
the executable files to the "bin" subdirectory (e.g. SUN4/bin) and
copies the library files to the "lib" subdirectory (e.g. SUN4/lib).
Actually it doesn't copy them, IT MAKES A HARD LINK, in order save
on disk space. System administrators may wish to change the destination
of the install (e.g. to /usr/local/bin and /usr/local/lib) and to
change the "ln" commands to "cp" or "install" as they wish.
Related to this are the directories "run_demos" and "run_isis". As
distributed, the "run_isis" directory is set up to run the binaries
out of the "bin" subdirectory, while the "run_demos" directory runs
the programs out of "protos" and "util". At Cornell we use this
organization so that we can test out the system in "run_demos" before
doing a "make install" to the public directories.
make clean:
This deletes the superfluous .o files in the binary areas.
make realclean:
This does a "make clean" and in addition deletes all the executable
and binary files.