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

Chapter 10 245
Technical Articles
Developer’s Kit for Java/iX
shell/iX> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:(add your stuff here)
Example of setting LD_LIBRARY_PATH from the CI:
:setvar LD_LIBRARY_PATH "/usr/local/java/latest/lib/PA-RISC/green_threa
ds:
(add your stuff here)"
Again, we specify a colon-separated list of directories to search. In this
case, we're providing the locations to search for library (XL) files that
contain native (that is, platform-specific) code. The java classes—all the
files that go into classes.zip—are the same on all platforms. The
platform-specific code is written in C, and compiled into shared
libraries (XLs on MPE). The standard Java runtime libraries are in the
location shown on the MPE :SETVAR command above; the Java shell
wrappers will include this location automatically when running Java
from the shell. Users usually do not need to add additional locations to
this variable; it is used only if you have written (or obtained from a
third party) Java code that includes native (non-portable) code. One
example of such a library is the TurboIMAGE/XL class library for MPE,
which includes an XL that has the interfaces to the IMAGE/SQL
intrinsics.
THREADS_FLAG Variable
Example of setting from the shell:
shell/iX> export THREADS_FLAG=green
The THREADS_FLAG variable is only needed when running from the
shell, and tells the java shell wrappers to use the binaries found in the
green_threads subdirectory (when running from the CI, we've
already indicated this in our setting of the HPPATH variable). There are
two possible ways to implement multithreading when porting Java to a
new platform: using kernel threads (with binaries in the
native_threads directory) or using library threads (with binaries in
the green_threads directory). The current MPE implementation uses
green_threads, although a native_threads version may be
developed in the future. If so, the THREADS_FLAG variable could be set
to native to select the kernel threads implementation (and the
HPPATH variable would be changed for CI users to select the
native_threads directory).
DISPLAY Variable
Example of setting from the shell:
shell/iX> export DISPLAY=sysname:0
Example of setting from the CI:
:setvar DISPLAY "sysname:0"
The DISPLAY value is used by the AWT and Applet classes to locate the
display device. Only X-Windows compatible display devices (UNIX
workstations, X-terminals, or PCs running X-Windows emulation
software) are supported for the display device. Most HP 3000 Java