/usr/local/oseFor example, OSE version 4.0 would be installed in the directory,
/usr/local/ose/4.0and as a result you should include the directory,
/usr/local/ose/4.0/binin your path. If you are using a Bourne shell, to add the OSE bin directory to your path, you would include the following in your login file:
PATH="/usr/local/ose/4.0/bin:$PATH"If you are using a C shell, you should use the following:
export PATH
set path = ( /usr/local/ose/4.0/bin $path )The scripts in this directory are generic and will work for whatever host architecture you are actually on. Where binaries must be run by these scripts, you must indicate the host architecture you are using by setting the OSE_HOST environment variable. For example:
OSE_HOST=SPARC_SUN4You should check with your OSE administrator as to what you should set this variable to at your own site. Alternatively, you can run the `ose-info' program from the OSE bin directory given above. This program will also give you an indication as to the C++ compilers for which OSE has been installed.
export OSE_HOST
/usr/local/ose/4.0/manAlternatively, you can run the `ose-man' program from the OSE bin directory.
/pkg/ose/4.0after originally being installed in some other location, you should set the OSE_ROOT environment variable to:
/pkg/oseThe OSE_ROOT variable should not include the name of any specific version. If a version of OSE is moved, the last component of the pathname should still be `ose'.
You should check with the administrator for OSE at your site as to the precise location of OSE on your system, and whether it is necessary to set the OSE_ROOT environment variable.