|
|
|
|
|
|
compilation(5)
Name
compilation—Instructions for compilation of BEA Tuxedo ATMI system application components.
Description
In order to compile application clients and servers, and subroutines that are link edited with the BEA Tuxedo system, programmers need to know:
A programmer who has finished writing code modules and is ready to build an executable program must:
The BEA Tuxedo system provides two commands that perform both of these operations for client and server modules: buildclient() and buildserver(), respectively. If you run one of these commands to perform both operations, be sure to specify, on the command line, the libraries with which your files need to be link edited. (For details, see buildclient(1) or buildserver(1) in the BEA Tuxedo Command Reference.)
Link editing must be done by running buildclient or buildserver, but the system allows more flexibility about how compiling is done. If you prefer, you can use the compile command of your choice to compile your files, and then run buildclient or buildserver to perform the link editing.
This rest of this reference page specifies the header files and environment variables required for various types of programs.
Basic BEA Tuxedo System
In terms of header file sequence, UNIX header files should always be included before any BEA Tuxedo system header files. Commonly used UNIX header files are stdio.h and ctype.h.
Environment Variables
The following environment variables should be set and exported:
Note: More information about these variables can be found in Programming a BEA Tuxedo Application Using C, Programming a BEA Tuxedo Application Using COBOL, and Setting Up a BEA Tuxedo Application.
After the system has been built with shared libraries and before you execute a client, you must set a variable that defines the location of the shared libraries.
|
On this platform . . . |
Set the following environment variable . . . |
|---|---|
|
All platforms except HP-UX and AIX |
LD_LIBRARY_PATH=$TUXDIR/lib |
|
HP-UX |
SHLIB_PATH=$TUXDIR/lib |
|
AIX |
LIBPATH=$TUXDIR/lib |
Note: More information about options for servers can be found on the servopts(5) reference page.
FML Programs
In terms of header file sequence, C programs that call FML functions should include the following header files, in the following order:
#include <UNIX_header_files> (if needed by the application)
#include "fml.h"
Compilation of FML Programs
To compile a program that contains FML functions, execute:
cc pgm.c -I $TUXDIR/include -L $TUXDIR/lib -lfml -lengine -o pgm
where pgm is the name of the executable file.
If the -L option is not locally supported, use the following command, instead:
cc pgm.c -I $TUXDIR/include $TUXDIR/lib/libfml.a $TUXDIR/lib/libengine.a -o pgm
Note: The order in which the libraries are specified is significant. Use the order given above.
Compiling FML VIEWS
To use the FML view compiler, execute the following:
viewc view_file
Here view_file is a set of one or more files containing source view descriptions.
Note: viewc invokes the C compiler. The environment variable CC can be used to designate the compiler to use. The environment variable CFLAGS can be used to pass a set of parameters to the compiler.
Environment Variables for FML
The following environment variables should be set and exported when running an application that uses FML.
The following environment variables should be set and exported when executing viewc.
See Also
buildclient(1), buildserver(1), viewc, viewc32(1)
cc(1), mc(1) in a UNIX system reference manual
|
|
|
|
|
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|