next up previous contents
Next: Conventions used in this Up: GRASP Installation Previous: Making the GRASP binaries   Contents

Stupid Pet Tricks

There are a number of simple things that one can do during or after the installation process that may make GRASP easier to maintain and/or use at your site. For example, if is often extremely convenient for debugging purposes to have a GRASP library (libgrasp.a) constructed with all the symbol table information turned on, and another library constructed with all the optimization switches turned on. Users who want their code to run as fast as possible can link to the optimized library. Users who want to track down problems within GRASP, or to step through internal GRASP functions can link to the debug library. You can accomplish this easily by building two separate GRASP libraries, as follows. (Note: since the normal C-compiler debugging option is -g the debug library has a _g appended to its name.) Your GRASP installation will now contain two GRASP libraries: /usr/local/GRASP/lib/libgrasp.a and /usr/local/GRASP/lib/libgrasp_g.a and two sets of executables, in
[4]/usr/local/GRASP/bin and /usr/local/GRASP/bin_g.

Another useful trick is if you are building versions of GRASP for several different architectures, on a shared /usr/local/ disk. Here the procedure is the following:

This method will avoid duplication of source files, documentation, etc, while still providing a set of libraries and executables for different machine types.


next up previous contents
Next: Conventions used in this Up: GRASP Installation Previous: Making the GRASP binaries   Contents
Bruce Allen 2000-11-19