Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

244 Chapter 10
Technical Articles
Developer’s Kit for Java/iX
PATH (or HPPATH) Variable
Example of setting PATH from the shell:
shell/iX> export PATH=$PATH:/usr/local/java/latest/bin
Example of setting HPPATH from the CI:
:setvar HPPATH HPPATH+",/usr/local/java/latest/bin/PA-RISC/green_threads"
These variables are not Java-specific, but rather the standard path
variables used to search for executable program files. The Java
executable program files are in the directory shown for the HPPATH
variable. When executing Java from the CI, the actual program binary
files are executed. When executing Java from the shell, we do not
execute the Java program files directly, but instead execute shell
"wrapper" scripts that are in the directory indicated by the PATH
statement above. These shell scripts set standard env variables for us
(such as CLASSPATH and LD_LIBRARY_PATH, shown below), so that we
don't need to specify values for these unless we wish to add to or replace
the standard settings.
CLASSPATH Variable
Example of setting CLASSPATH from the shell:
shell/iX> export CLASSPATH=$CLASSPATH:(add your stuff here)
Example of setting CLASSPATH from the CI:
:setvar CLASSPATH "/usr/local/java/latest/lib/classes.zip:(add your stuff
here)"
Like the PATH variable, the CLASSPATH variable is a colon-separated
list of directories (or zipped archive files) to search. While the PATH and
HPPATH variables list the directories to search for program files, the
CLASSPATH variable lists the directories to search for Java classes.
The standard Java classes (such as those that make up the java.lang,
java.io, and java.net packages) are all bundled together in a single
ZIP format archive file, called classes.zip and stored at the location
shown in the :SETVAR command above. When running from the shell,
the wrapper script sets the CLASSPATH for you to include this file; when
running from the CI, you must create a CLASSPATH variable to include
the classes.zip file. In either case, any additional classes, such as
application or applet-specific classes you have written or obtained from
a third party, must also be listed in the CLASSPATH. Because locations
on the CLASSPATH are searched in the order you specify, best
performance is obtained when you order the directories on the
CLASSPATH so that the directories containing the most
frequently-accessed classes are listed first. (In most cases, this means
that the standard classes.zip file should come before any others).
LD_LIBRARY_PATH Variable.
Example of setting LD_LIBRARY_PATH from the shell: