Command Reference
buildobjserver
—Constructs a CORBA server application.
buildobjserver [-v] [-o
name
] [-f
firstfile-syntax
]
[-llastfile-syntax
] [-r
rmname
][-t]
Use the buildobjserver
command to construct a CORBA server application. The command combines the files specified with the -f
and -l
options with the main routine and the standard CORBA libraries to form a server application. The server application is built using the default C++ compiler provided for the platform.
All specified .c
and .cpp
files are compiled in one invocation of the compilation system for the operating system in use. Users may specify the compiler to be invoked by setting the CC
environment variable to the name of the compiler. If the CC
environment variable is not defined when buildobjserver
is invoked, the default C++ language compile command for the operating system in use is invoked to compile all .c
and .cpp
files.
Users may specify options to be passed to the compiler by setting the CFLAGS
or the CPPFLAGS
environment variable. If CFLAGS
is not defined but CPPFLAGS
is defined when buildobjserver
is invoked, the command uses the value of CPPFLAGS.
Specifies that the buildobjserver
command should work in verbose mode, and it writes the compile command to standard output.
Specifies the name of the server application generated by this command. If a name is not supplied, the application file is named server.
type
, where type
is an extension that indicates which operating system is being used for the application. For example, an application that is called server on a UNIX system is called server.EXE
on a Windows NT system.
Specifies the file to be included first (that is, before the CORBA libraries) in the compile and link phases of the buildobjserver
command. For a description of the three ways to specify files, see the table entitled Specifying the First Filename(s).
Specifies the file to be included last (that is, after the CORBA libraries) in the compile and link phases of the buildobjserver
command. For a description of the three ways to specify files, see the table entitled Specifying the Last Filename(s).
Specifies the resource manager associated with this server. The value rmname
must appear in the resource manager table located in $TUXDIR/udataobj/RM
on UNIX systems or %TUXDIR%\udataobj\RM
on Windows NT systems.
Using the rmname
value, the entry in $TUXDIR/udataobj/RM
or %TUXDIR%\udataobj\RM
automatically includes the associated libraries for the resource manager and sets up the interface between the transaction manager and the resource manager. The value TUXEDO/SQL
includes the libraries for the BEA Tuxedo System/SQL resource manager. Other values can be specified as they are added to the resource manager table. If the -r
option is not specified, the null resource manager is used by default.
Invokes help: information that is useful when running the buildobjserver
command. No other action results.
Indicates the compiler to use to compile all files with .c
or .cpp
file extensions that are passed in through the -l
or -f
option.
Specifies any arguments that are passed as part of the compiler command line for any files with .c
or .cpp
file extensions. If CFLAGS
is not available in the buildobjserver
command environment, the buildobjserver
command checks for the CPPFLAGS
environment variable.
Note: Arguments passed by the CFLAGS
environment variable take priority over the CPPFLAGS
environment variable.
Contains a set of arguments that are passed as part of the compiler command line for any files with a .c
or .cpp
file extension. This option is used in addition to the command-line option -I$TUXDIR/include
on a UNIX system, or the command-line option /I%TUXDIR%\include
on a Windows NT system, which is passed automatically by the buildobjserver
command. If CPPFLAGS
is not available in the buildobjserver
command environment, no compiler commands are added.
List of directories that contain shared objects to be used by the compiler, in addition to CORBA shared objects. A colon (:) is used to separate names of directories. Some UNIX systems require different environment variables: for HP-UX systems, use the SHLIB_PATH
environment variable; for AIX, use LIBPATH
.
The buildobjserver
command is not supported on client-only CORBA systems.
The following example builds a CORBA server application on a UNIX system using the emp_s.cpp
and emp_i.cpp files
:
buildobjserver -r TUXEDO/SQL -o unobserved
-f "emp_s.cpp emp_i.cpp"
The following example shows how to use the CC
and CFLAGS
environment variables with the buildobjserver
command. The example also shows how to link in the math library, using the -f
and -lm
options, in a Bourne or Korn shell (on a UNIX system):
CFLAGS=-g CC=/bin/cc \
buildobjserver -r TUXEDO/SQL -o TLR -f TLR.o -f util.o -l -lm
The following example shows how to use the buildobjserver
command on a UNIX system with no resource manager specified:
buildobjserver -o PRINTER -f PRINTER.o
The following sections show sample RM files for all supported operating system platforms:
Oracle_XA;xaosw;C:\Orant\rdbms73\xa\xa73.lib
C:\Orant\pro22\lib\msvc\sqllib18.lib
Oracle_XA:xaosw:-L$ORACLE_HOME/rdbms/lib
-L$ORACLE_HOME/precomp/lib -lc
-L/home4/m01/app/oracle/product/7.3.2/lib -lsql -lclntsh
-lsqlnet -lncr -lcommon -lgeneric -lepc -lnlsrtl3 -lc3v6
-lcore3 -lsocket -lnsl -lm -ldl -lthread
Oracle_XA:xaosw:-L${ORACLE_HOME}/lib -lxa
${ORACLE_HOME}/lib/libsql.a -lsqlnet -lncr -lsqlnet
${ORACLE_HOME}/lib/libclient.a -lcommon -lgeneric -lsqlnet
-lncr -lsqlnet ${ORACLE_HOME}/lib/libclient.a -lcommon
-lgeneric -lepc -lepcpt -lnlsrtl3 -lc3v6 -lcore3
-lnlsrtl3 -lcore3 -lnlsrtl3 -lm
Oracle_XA:xaosw:-L${ORACLE_HOME}/lib -lxa -lsql -lsqlnet
-lncr -lclient -lcommon -lgeneric -lepc -lnlsrtl3 -lc3v6
-lcore3 -lm -lld
Oracle_XA:xaosw:-L${ORACLE_HOME}/lib -lclntsh