Setup on UNIX
This procedure explains how to configure Views on a UNIX® station. You must have on hand the following installation information:
Installation Directory: Views components are normally installed in the
/usr/local/perforce/ directory, including
/usr/local/perforce/viewsXX (where
XX stands for the version number). If you install Views in another directory, replace subsequent references to the default directory with your actual installation directory.
System Name: The name of your
<system> directory can be found in the
README file delivered with the product. For example,
x86_rhel5.0_4.1. In the following instructions, replace
<system> with your actual system name.
Format Name: For each supported system, at least two formats are available. One format is for using static libraries, the format name starts with 'stat' for all systems. The other format is for using shared or dynamic libraries, the format name starts with 'shared' on UNIX/Linux platforms and 'dll' for Windows platforms.
To configure Views on UNIX, do the following:
1. Set the ILVHOME variable.
The shell variable ILVHOME must be set to the Views installation directory.
If you use
sh or one of its derivatives, such as
ksh or
bash, type:
$ ILVHOME=/usr/local/perforce/viewsXX
$ export ILVHOME
If you use
csh or
tcsh, type:
% setenv ILVHOME /usr/local/perforce/viewsXX
2. Set up the shared library path variable.
On most operating systems, the directories containing dynamic libraries must be added to an environment variable: SHLIB_PATH on HP-UX, LIBPATH on AIX®, LD_LIBRARY_PATH on the others.
If using
sh or one of its derivatives, type:
$ LD_LIBRARY_PATH=$ILVHOME/lib/<system>/<shared format>:$LD_LIBRARY_PATH
$ export LD_LIBRARY_PATH
If using
csh or
tcsh, and the variable
LD_LIBRARY_PATH is not already defined, type:
% setenv LD_LIBRARY_PATH $ILVHOME/lib/<system>/<shared format>
If using
csh or
tcsh, and the variable
LD_LIBRARY_PATH is already defined, type:
% setenv LD_LIBRARY_PATH $ILVHOME/lib/<system>/<shared format>:$LD_LIBRARY_PATH
This can be automated by putting the above commands in your shell startup file (either .profile if using sh, or .login if using csh).
Published date: 05/24/2022
Last modified date: 02/24/2022