CORBA 2.3.7 Programmer's Guide for C++

> export JAVA_HOME=/usr/tandem/java
> export JREHOME=$JAVA_HOME/jre
> export
CLASSPATH=.:$NSD_ROOT/lib/jorb.jar:$NSD_ROOT/lib/jts.jar:$NSD_ROOT/lib/ejb.jar
> add_define =_SRL_01 class=map file=$NSD_SRL_SUBVOL.NSDSRL
> export CLASSPATH=.:$CLASSPATH:$NSD_ROOT/idl/nsdidl.jar:
$NSD_ROOT/lib/jorb.jar:$NSD_ROOT/lib/JTS.jar
> export PATH=$PATH:$NSD_ROOT/bin:$COMP_ROOT/usr/lib:$JAVA_HOME/bin
$NSD_ROOT designates the root directory where NonStop CORBA files reside. This guide sometimes refers to
directory names relative to $NSD_ROOT; in these cases, the notation $NSD_ROOT means your setting of the
NSD_ROOT variable.
JAVA_HOME designates the root directory where NonStop Server for Java files reside. The jorb.jar and
JTS.jar files reside in the $NSD_ROOT/lib directory. To add them to the CLASSPATH use the env.sh script.
The add_define sets a Guardian define from OSS to point to the NonStop CORBA SRL. Guardian uses this
define to associate an executable with an SRL when the executable runs.
CLASSPATH is an environment variable that tells the JVM and where to find the class libraries, including
user-defined class libraries.
PATH specifies the order in which to search directories for a command typed at the osh prompt.
OSS Development and Debugging Tools
You use the following OSS commands and utilities to develop your application:
make
This utility helps you build and maintain an application that consists of multiple, interdependent modules.
You use a file, called Makefile by default, to describe the dependencies among program modules. Thereafter,
when you modify a module on which other modules depend, the make utility automatically initiates
recompilation of the dependent modules. The NonStop CORBA sample programs use a Makefile to perform
all the steps for building and configuring applications: running the IDL compiler, compiling and linking
application programs.
c89
This utility is the front end for the C++ compiler. You can invoke c89 from within the make file.
nld
This utility is the native (TNS/R) linker. It links one or more TNS/R native object files to produce an
executable or relinkable native object file. You can run the nld utility from either the Guardian or the OSS
environment. c89 automatically invokes the nld utility. Therefore, in most cases you need not use nld
explicitly when creating application executable files.
nm
The nm command writes the name list of each specified object file to the standard output file. The nm
command displays symbolic information appearing in an object file, executable file, or object-file library. nm
can be used to find symbols that show up in unresolved external error messages.