INSTALLING The Shift-Right Open Repository's BENV Build Environment
================================================================================

  1. Package-Root, Tool-Root, and Source-Root directories.  For these 
     instructions, the Package-Root directory is the top level directory of the 
     unzipped tar file (i.e. the one that contain the changelog.txt file and the
     directories such as, projects/, build/, src/, etc.  THe Tool-Root directory
     is where on your machine you plan to install the tools required by the
     BENV build environment.  The Source-Root directory is the where on your
     machine you plan to install the XMK source tree.

  2. Copy/Move the following directories from the Package-Root directory to
     the Source-Root directory:
        build/
        projects/
        iheaders/
        hostlinks/
        src/
        xsource/

  3. From the Package-Root, move the contents of the xxxx-tools directory to 
     the Tools-Root directory. The recommended parent directory for Tool-Root
     directory is /tools.  However, the tools can be located anywhere.  Set the 
     environment variable BENV_LATEST_ROOT to the actual parent directory used. 
     For Unix (from the Package-Root directory):
        $ cd unix-tools/tools
        $ mv latest /tools/latest

     For Windows (from the Package-Root directory):
        c:> cd win32-tools/tools
        c:> ren latest \tools\latest
 
  4. For Unix. 
        In the Source-Root directory, Update the symbolic file links contained
        in the hostlinks/ directory to point to the appropriate tools. 
        For example, starting from the Source-Root directory:
           $ cd /<repositoryroot>/hostlinks/Linux/native
           $ ln -s /usr/bin bin
 
     For Windows.
        a) Create the directory \tmp on the same drive that BENV tools where 
           installed on.  This directory is needed by the UNIX shell emulator 
           that is part of the BENV tools. For example: if the BENV tools are 
           installed at c:\tools then create c:\tmp.
        b) Insure that the needed host tools (compiler, linker, etc.) are in the 
           "command path".  Typically, this done using the hostlinks directory 
           and symbolic links.  But, since Windows does not support symbolic 
           file links, this step has to be done manually.  For example: if you 
           are using the Visual C/C++ compiler, put the vcvars32.bat somewhere 
           in your command path.  Then when a developer begins working, he/she 
           simply runs the batch file.
 
  5. Each developer must modify his/her login profile with basic information 
     about BENV.
     For Unix (using the Bash shell):        
        Add the following the lines to your login profile.  
        NOTE: it assumes that the ‘latest’ component is stored at 
              /tools/latest/benv.

            # Build Environment
            export BENV_LATEST_ROOT=/tools/latest
            export PATH=$PATH:$BENV_LATEST_ROOT/benv

     For Unix system’s where GNU Make is not the native make, you must set an 
     additional environment variable to inform BENV of the executable name of 
     the GNU Make tool.

            # Solaris 
            export BENV_GMAKE=gmake

     For Windows:
        Make the following modification to your environment. 
        NOTE: it assumes that the ‘latest’ component is stored at 
              c:\tools\latest\benv.

            set BENV_LATEST_ROOT=c:\tools\latest
            set PATH=%PATH%;%BENV_LATEST_ROOT%\benv