Setup and Startup

2.3 The Tornado Host Environment

Tornado requires host-system environment variables for the following purposes:

Tornado-specific environment variables reflect your development environment: what sort of host you are using, where Tornado was installed on your system, and where on your network to find the Tornado registry for development targets.

Your shell search path must specify how to access Tornado tools.

2.3.1 Environment Variables for Tornado Components discusses all Tornado environment variables.

You can also set X Window System resources to allow the Tornado tools to benefit from color or grayscale displays; see 2.3.4 X Resource Settings.

2.3.1 Environment Variables for Tornado Components

Specify the location of Tornado facilities by defining the following environment variables on your development host:

WIND_BASE

installation directory for Tornado

WIND_HOST_TYPE

name of host type; see Table 2-1

WIND_REGISTRY

registry host; see 2.2 Setting up the Tornado Registry

PATH

shell search path; add $WIND_BASE/host-os/bin directory

LD_LIBRARY_PATH

dynamic library search path for Solaris;
add Tornado $WIND_BASE/host/sun4-solaris2/lib directory

SHLIB_PATH

dynamic library search path for HP-UX;
add $WIND_BASE/host/parisc-hpux10/lib directory

The Tornado installation includes a wind/host/host-os/bin directory of tools that run on your development host. The values for host-os match those listed in Table 2-1 for WIND_HOST_TYPE. Add the wind/host/host-os/bin directory for your host to the UNIX shell search path (PATH).

Table 2-1: Values for WIND_HOST_TYPE and host/bin


Host	Host OS	WIND_HOST_TYPE

HP9000 series 700	HP-UX 10.2x	parisc-hpux10
Sun-4	Solaris 2.x	sun4-solaris2

Example Environment Setup Using C Shell

If you use the C shell, add lines like the following to your .cshrc to reflect your Tornado development environment. After you modify the file, be sure to source it and execute the rehash command.

The following example is for a Sun-4 host running Solaris 2.x, in a network, whose Tornado registry is on host mars:

setenv WIND_BASE  /usr/wind 
setenv WIND_HOST_TYPE sun4-solaris2 
setenv WIND_REGISTRY mars 
setenv PATH ${WIND_BASE}/host/sun4-solaris2/bin:${PATH} 
setenv LD_LIBRARY_PATH ${WIND_BASE}/host/sun4-solaris2/lib:${LD_LIBRARY_PATH}

Example Environment Setup Using Bourne Shell (or Compatible)

If you are using the Bourne shell (or a compatible shell, such as the Korn shell or Bash), add lines like the following to your .profile to reflect your Tornado development environment. Be sure to source the file (using the "." command) after you modify the file.

The following example is for an HP9000 host in a network whose Tornado registry is on host venus:

WIND_BASE=/usr/wind; export WIND_BASE 
WIND_HOST_TYPE=parisc-hpux10; export WIND_HOST_TYPE 
WIND_REGISTRY=venus; export WIND_REGISTRY 
PATH=$WIND_BASE/host/parisc-hpux10/bin:$PATH; export PATH 
SHLIB_PATH=$WIND_BASE/host/parisc-hpux10/bin:$SHLIB_PATH; export SHLIB_PATH

2.3.2 Environment Variable

Solaris 2 Hosts

If your development host runs Solaris 2, you must also modify the value of LD_LIBRARY_PATH to include the shared libraries in /usr/dt/lib, /usr/openwin/lib, and $WIND_BASE/host/sun4-solaris2/lib.

If you use the C shell, include a line like the following in your .cshrc:

setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/usr/dt/lib:/usr/openwin/lib

If you use the Bourne shell (or a compatible shell), include lines like the following in your .profile:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/dt/lib:/usr/openwin/lib 
export LD_LIBRARY_PATH

HP-UX Hosts

If your development host runs HP-UX, you must also modify the value of SHLIB_PATH to include $WIND_BASE/host/parisc-hpux10/lib.

2.3.3 Environment Variables for Convenience

Certain other environment variables, though they are not required for Tornado, can make the tools fit in better with your site or with your habits. The following environment variables are in this category:

EDITOR

When you request an activity in a Tornado tool that involves editing text files, the Tornado tools refer to this variable to determine what program to run. The default is vi, if EDITOR is not defined.

PRINTER

When any Tornado tool generates a printout at your request, it directs the printout to the printer name specified in this variable. The default is lp, if PRINTER is not defined.

2.3.4 X Resource Settings

Tornado has resource definitions to cover the range of X Window System displays. For better use of color or grayscale displays with Tornado, set customization resources in your X-resource initialization file (usually a file named .Xdefaults or .Xresources in your home directory). There are three possible values for these resources:

undefined

The general-purpose default; suitable for monochrome displays.

-color

For color displays.

-grayscale

For grayscale displays.

% xrdb -merge .Xdefaults

NOTE: X servers consult the resource-initialization file automatically only when they begin executing. To force your display to use new properties immediately, invoke the utility xrdb. For example, after modifying X resources in .Xdefaults, execute the following:

The following example (for a color display) shows customization settings specified explicitly for each of the Tornado tools:

Browser*customization: -color 
CrossWind*customization: -color 
Dialog*customization: -color 
Launch*customization: -color 
Tornado*customization: -color

Alternately, you can set customization globally for all tools that use this property. The following example does this for a grayscale display:

*customization: -grayscale

WARNING: If you set the customization property globally, it may affect applications from other vendors, as well as the Tornado tools.

For more information about X resources in Tornado, see E. X Resources.