TOC PREV NEXT



B.1 pRISM+ Variables for the Windows Environment

There are three sections of environment variables:

  1. Global variables
  2. User Related variables
  3. Tools Related variables

The global variables are:

Global Variable
Content
PRISM_INSTALL_DIR
Directory, where the pRISM+ product is installed.
PRISM_VERSION
Optional variable to qualify an optional service pack
HOST
Host computer's OS, here "win_32"
(alternatively solaris or hpux are used in pRISM+ for Unix.).
CPU_FAMILY
Names the CPU-Type, pRISM+ is designed for! Often also referenced in the documentation as "target_name".
(This value is one of: 68k, arm, mips, ppc or x86.)
CPU_FAMILY_3LETTERS
Names the CPU-Type, pRISM+ is designed for! In filenames and names of working environments this 3 letter version of $CPU_FAMILY used.
(This value is one of: 68k, arm, mip, ppc or x86.)
COMP_TOOL
Brand of the compiler. This is used via the variable PLATFORM to determine the platform depending name of the Compiler/Linker specific part of the SNiFF+'s Make Support.
(This value is one of: diab, arm or cadul.)
PLATFORM
Prefix of the filename of the Compiler/Linker specific part of the SNiFF+'s Make Support. It is generated by the expression:
PLATFORM=${COMP_TOOL}$CPU_FAMILY}_${HOST}
(This value is one of: armarm_win32, cadul_x86_win32, diab68k_win32, diabmip_win32 or diabppc_win32.)

The user related variables

User Related Variable
Content
VISUAL
Terminal Emulation of the MKS Toolkit shell (Korn Shell)
It is set to emacs in respect to the use of the arrow keys for command history retrieval (Has been in SNiFF+ 3.0.2 set to vi).
ISI_PROJECT_NUM
Customer related number to identify the current project.
This value is used to fill out the License registration form and the problem report.
(Set to eval in case of an evaluation.)
gt:
PSS_ROOT
Points to the location of the subdirectory containing all pSOSystem related files. It may be anywhere in the drive space of the hosdt. (It is not restricted to be located under $PRISM_INSTALL_DIR!)
Usually the name is composed from: pss$CPU_FAMILY.<version>
PSS_ROOT_FOR_SNIFF_PWE
Points to the location of the subdirectory containing the pSOSystem folders drivers, bsps and include.
For comile runs outside SNiFF+ the variable contains the value of the variable PSS_ROOT.
For comile runs from within SNiFF+ the variable contains the value of the variable PSS_USER_PWE.
For compatibility reason the variable is set by default to PSS_ROOT in both cases. This may be switches in the file $PSS_ROOT/bin/win32/psosmake.ksh
USERNAME
Name of the user logged into this computer's OS. It is retrieved by the program MyName.exe.
Caution for Windows 9x users: If you do not log in, many actions fail due to a lack of a UserName!
PSS_BSP
Points to the location of the subdirectory containing all pSOSystem BSPs.
It has to be located at $PSS_ROOT/bsps/<BSP name> for SNiFF+ subsystem to function correctly!
If you have already set this value from outside pRISM+, the found setting is taken!
BSP_TYPE
For ARM users only:
Selects the mode the BSP is used for:
  • 32l = 32-bit ARM mode Little Endian
  • 32b = 32-bit ARM mode Big Endian
  • 16l = 16-bit THUMB mode Little Endian
  • 16b = 16-bit THUMB mode Big Endian
HOME
Points to the location of the subdirectory containing all user related files like sources.
If not set already it is set to $PSS_ROOT/users/$USERNAME.
PSS_USER_SHARED
Location of a directory holding the SSWEs, the SOWE and the RWE.
This defaults to $PRISM_INSTALL_DIR/users/common
PSS_USER_RWE
Location of a directory holding the Repository (Version Control files).
This defaults to $PSS_USER_SHARED/Repository
PSS_USER_SOWE
Location of a directory holding the SOWE (Not yet used but already prepared).
This defaults to $PSS_USER_SHARED/SharedObjectArea
PSS_USER_SSWE
Location of a directory holding the SSWE for the User's Code (Existing Codebase).
This defaults to $PSS_USER_SHARED/SharedProjectArea
PSS_USER_PWE
Location of a directory holding the PWE.
This defaults to $HOME/psos${CPU_FAMILY}_pwe
PSS_WE_NAME_RWE
Working environment name for the RWE
This defaults to RWE:pSOSystem-Repository
PSS_WE_NAME_SOWE
Working environment name for the soWE
This defaults to SOWE:pSOSystem-${CPU_FAMILY}-Objs
PSS_WE_NAME_SSWE
Working environment name for the RWE
This defaults to SSWE:pSOSystem-${CPU_FAMILY}
PSS_WE_NAME_USER_SSWE
Working environment name for the USER SSWE
This defaults to SSWE:pSOSystem-${CPU_FAMILY}-User
PSS_WE_NAME_PWE
Working environment name for the RWE
This defaults to adm PWE:${CPU_FAMILY}-Private
SNIFF_RESOURCE_DIR
Points to the location of the subdirectory containing all user related SNiFF+ settings.
This variable is not used by default, since by default $SNIFF_DIR/Profiles/$USERNAME is used.

The tools related variables

Tools Related Variable
Content

For pRISM+ ManagerInstallation:
PRISM_DIR
Location of pRISM+ tool files.
TCL_LIBRARY
Used by pRISM+
LOGNAME
Same as USERNAME.



For SNiFF+ Installation:
SNIFF_VERSION
Version of the installed SNiFF+ product.
(Introduced with SNiFF+ Version 3.2.)
SNIFF_DIR
Location of the SNiFF+ installation.
SNIFF_INTEGRATION_DIR
Location of the Integration of SNiFF+ 3.2 in pRISM+ 2.0, usually $SNIFF_DIR/integrations/pRISM2.0
SNIFF_MAKE_CMD
Not used in this integration. Was used for SNiFF+ 3.0.2!



For MKS Toolkit Installation:
ROOTDIR
Location of the MKS Toolkit.
SHELL
Points to the location of the Korn Shell executable.
Although SNiFf+ V3.2.x comes with the GNU bash in the file sh.exe, pRISM+ needs the Korn Shell out of the MKS Toolkit!)
TMP_DIR
Location of a temporary disk space for temporary files.
ENV
Location of a common customization of the Korn Shell.



For CORBA (ORBIX) Installation:
IT_CONFIG_PATH
Location of the configuration parameters for the ORBIX daemon.



For FlexLM Licensing Installation:
LM_LICENSE_FILE
Location of the file license.dat (usually in $PSS_ROOT/licenses/license.dat.
Here is either a Temporary Evaluation License, Node Locked License or Floating License referenced.



For DIAB-SDS Compiler Installation:
DIABLIB
Location of the DIAB-SDS Compiler/Linker installation



For DIAB-SDS Debugger SingleStep Installation:
SDS_VERSION
Introduced with Version 7.5.



For ARM SDK Compiler/Debugger Installation:
ARM
Location of the ARM SDK Compiler/Debugger installation
ARMLIB
Location of the ARM SDK Linker libraries
ARMINC
Location of the ARM SDK Compilerer include files



For CAD-UL Compiler/Debugger Installation:
CC386TMP
Temporary directory for Compiler/Linker usage.


The environment variables are set in the startup script env$CPU_FAMILY.ksh.
Here also is the directory structure generated to hold the directories PSS_USER_* and the example existing codebase user_pdemo.
For user specific customization of the startup script there is the script userenv.ksh in the HOME directory included at the end of the scriptenv$CPU_FAMILY.ksh.


TOC PREV NEXT