Build Environment


This section describes the hardware and software requirements for the PJES build environment and its setup procedures. See Build Environment Procedures for a description of how to use the PJES build environment to build the PJAE. See Build Environment Implementation for a description of the tools and build process of the PJES build environment.

Solaris

Hardware Requirements

Software Requirements

Software Setup

The PJES build environment and the JDK use the environment variables described in the table below. Some of these environment variables can cause name conflicts and should be defined correctly so that they do not include directories for JDK versions that are not compatible with the PJES build environment.

Environment Variables
VariableDescription
LANG The system locale.
CLASSPATH The search path used by the Java virtual machine to find class files.
LD_LIBRARY_PATH The search path for finding shared libraries that contain the implementations of native methods.

The following steps describe how to setup the PJES build environment on a Solaris system:

  1. The PJES build environment requires a development system with a system locale based on the ISO 8859-1 (Latin-1) character set. The following C shell command sets the system locale to English/US.

    setenv LANG en_US
    

  2. Modify the CLASSPATH environment variable to include only class directories appropriate for building the PJAE.

  3. Define the PATH variable so that it includes the directories with the appropriate tools. At a minimum, this should include the directories described in the table below.

    The PATH variable is usually defined in a startup file for a shell program like csh, sh, ksh or bash. It is usually best to add these directories to the front of the list in the PATH variable to avoid name conflicts.

    Directories in the PATH Variable
    ExampleDescription
    /usr/local/java/jdk1.1.7/solaris/bin JDK programming tools, like javac and javah.
    /usr/local/bin Zip compression and archiving tools.
    /usr/local/bin GNU C Compiler.
    /usr/ccs/bin Solaris programming utilities.

    Here is a PATH environment variable definition for csh(1) based on the examples in the table above:

    setenv PATH ".:/usr/local/java/jdk1.1.7/solaris/bin\
                :/usr/local/bin:/usr/ccs/bin:/usr/sbin:/usr/ucb:/bin:/usr/bin:$PATH"
    

  4. If necessary, modify the LD_LIBRARY_PATH environment variable to include any shared libraries appropriate for building the PJAE.

Microsoft Windows NT

Hardware Requirements

Software Requirements

Software Setup

The procedure for setting up the PJES build environment under Microsoft Windows NT has three steps. Some of these steps can be condensed into a batch file or added to autoexec.bat.

  1. The PJES build environment requires a development system with a system locale based on the ISO 8859-1 (Latin-1) character set:

    1. Choose Control Panel->Regional setting->Region.

    2. Select English (United States).

  2. Run the VCVARS32.BAT script to configure the environment variables for Visual C++.
    vcvars32 x86
    

    This script defines the INCLUDE, LIB and PATH environment variables for use with the makefiles and scripts in the PJES build environment.

  3. Modify the CLASSPATH environment variable to include only class directories appropriate for building the PJAE.

  4. Modify the PATH environment variable to indicate where the Microsoft Assembler and MKS Toolkit executables are located. The PATH environment variable defines a list of directories that the MS-DOS shell uses as a search path for finding executable programs. Note that the PJAE also uses the PATH environment variable to search for DLL's that contain implementations of native methods.
    set PATH=C:\Program Files\MASM\bin;C:\Program Files\MKS\bin;%PATH%